Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:37
    MasterOdin commented #209
  • 05:37
    MasterOdin commented #209
  • 05:36

    MasterOdin on main

    Add a timeout to the url reques… (compare)

  • 05:36
    MasterOdin closed #207
  • 05:35
    MasterOdin synchronize #207
  • 04:05
    yosileyid commented #8258
  • 04:01
    yosileyid commented #8258
  • 01:30
    kbdharun labeled #9833
  • 00:49
    tldr-bot commented #9834
  • 00:48
    github-actions[bot] labeled #9834
  • 00:48
    kant opened #9834
  • 00:02
    github-actions[bot] unlabeled #9599
  • 00:02
    github-actions[bot] unlabeled #9786
  • 00:02
    github-actions[bot] labeled #9794
  • 00:02
    github-actions[bot] commented #9794
  • Feb 05 22:51
    waldyrious commented #6106
  • Feb 05 22:49
    waldyrious commented #6106
  • Feb 05 22:49
    waldyrious commented #6106
  • Feb 05 22:49
    waldyrious commented #6106
  • Feb 05 22:48
    waldyrious commented #6106
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
OMG this is bad, I got a lot of emails from PRs regarding CLAassistant.
waldyrious
@waldyrious:matrix.org
[m]
We might want to look into an alternative CLA system in the future... but for now I really don't think we'll have a way around the need for re-signing 😩
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Every PR is getting a CLA Prompt πŸ’₯ 😱.
waldyrious
@waldyrious:matrix.org
[m]
We should announce this somehow... maybe a tweet and a pinned issue in the repo, explaining that it's due to a simple typo fix in the CLA (https://gist.github.com/waldyrious/e50feec13683e565769fbd58ce503d4e/revisions), so that people aren't startled by CLA Assistant's new prompt...
12 replies
Emily Grace Seville
@EmilySeville7cfg
Hi! Can somebody review #9528 PR?
Emily Grace Seville
@EmilySeville7cfg
... and #9602 PR too :smile:
Emily Grace Seville
@EmilySeville7cfg
(dolist (user (tldr-members)) (message (format "Happy new year :smile:, %s!" user)))
1 reply
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Happy new year guys πŸŽ‰.
pixel aka chrissx
@chrissx:matrix.org
[m]
crap it doesn't send them because it's lazy
Emily Grace Seville
@EmilySeville7cfg
Hi `${user_names[@]}! :smile: What about to review these PRs: #9602, #9648, #9647?
sethi
@sethi:one.ems.host
[m]

Finally pushed to GitHub if anyone wants to peek at it.
It does not export to the format OPUS uses since honestly, I found it a bit confusing. ^-^'
But figured I can put this out for now if anyone wants to help clean it up or complain about my code. πŸ‘οΈ

(Feel free to complain about the name too or propose alternatives.)

https://github.com/tldr-pages/tldr-pages-dataset-gen

sethi
@sethi:one.ems.host
[m]

And I guess for those that are curious about the output but don't want to actually run it.

npm run tldr-translation-dataset-gen -- -s ../tldr/ -o dataset.csv -O (no builds yet)

https://gist.githubusercontent.com/SethFalco/d581e8d9753dd9def5e3fe715e3bbc0c/raw/0552d720d04ed689ff016e1609045e656b358216/dataset.csv

36,000~ mappings in total

3 replies
Emily Grace Seville
@EmilySeville7cfg
😁Looks pretty well. I'll takea closer look soon
Emily Grace Seville
@EmilySeville7cfg
what's the best option do u think:
  • {{optional/path/to/file}}
  • {{optional_path/to/file}}
  • {{path/to/optional/file}}
  • {{path/to/optional_file}}
    ?
5 replies
Emily Grace Seville
@EmilySeville7cfg
The problem is a limitation of example count. Sometimes 8 examples are not enough. I understand why such limitation exist, but for someone it may be annoying. Not for me, I'm okay with it as its standardized (I love everything standardized) :)
5 replies
Emily Grace Seville
@EmilySeville7cfg
I have a suggestion. I can create my own TlDr alternative with syntax I want. And leave everything here as u guys want if u want. But I would appreciate any assistance while creating my own project. I don't wanna restrict myself with readable syntax TBH, I am a programmar, I can write easily smth like that {{1..10}}?and make it render without question mark in different colors. I don't need numerous clients, I need just the best one. I don't need to depend on some outdated clients, don't want to constrain myself to non generic placeholders. Man pages are too long and not very standardized, and but it doesn't mean that their short alternative with rich syntax can't be created. I can stop submitting new PRs to change style guide.
waldyrious
@waldyrious:matrix.org
[m]

(Feel free to complain about the name too or propose alternatives.)

Seth I am aware that the current name is already a mouthful, but I'd feel it would be more intuitive to include "translation" somewhere in the title. Perhaps replace "dataset" with "translation-pairs"?

sethi
@sethi:one.ems.host
[m]
I'm fine with any name, are you thinking tldr-translation-pairs-gen (maybe singular pair is fine) then?
Maybe this is less accessible but tldr-i18n-pair-gen might be alright too and is shorter? πŸ€”
waldyrious
@waldyrious:matrix.org
[m]
I think tldr-translation-pairs-gen is clearer, but tldr-i18n-pair-gen is better than the current name.
sethi
@sethi:one.ems.host
[m]

Sure, will change the repo/name in a sec.
If anyone else has any qualms/ideas, now is a good time to share it! Would prefer if we dealt with any name (or other identity) related things before anyone finds or depends on the repo. (Though I'm not expecting that to happen atm anyway tbh.)

Soon will work on getting the OPUS format done so I can share it with them to host. \(^-^)/

Emily Grace Seville
@EmilySeville7cfg
I thought that I have to return back to TlDr. There are many things can be changed or improved here. And I will do it. First of all soon I am gonna suggest to use my TlDr client as a tldr-lint replacement and better render. It will be a breaking change as my client linting is way much stricter then tldr-lint. Then... I standardize all syntax and make style guide comprehensive. The goal is to make pages easy to read even making them a little bit harder (for someone) to write. But this is solvable by developing good IDE tooling. And at the end I propose a completely new placeholder syntax which will bw much better and more expensive than the current one. I am already thinking what it should be. And it definitely will be supported by my client.
3 replies
Emily Grace Seville
@EmilySeville7cfg

I suggest replace "path/to/file_or_directory" with "path/to/something". I wanna deprecate "or" completely as we are have syntax for alternatives via pipe character. Or we can just replace "path/to/file_or_directory" with a "path". If somebody thinks it's confusing I can also tell that "path/to/file" can be misinterpreted as everything is a file in Linux and file is not just a regular file. What we can do - "pin" placeholder semantics in our style guide and that's all, it's what already done for placeholders. BTW, I consider "or" as a bad design and that's why my client will reject such syntax and require pipe (or another placeholder if it's introduced, for instance what I've suggested). And I understand that it's a breaking change invalidating many pages. But I also think that's better to resolve design issues earlier than later.

Here is another issue - it's undefined how to specify multiple file extensions. We used square brackets for this but it's not defined by style guide. Square brackets in manpages used for optional arguments, and that's why they can be interpreted as optional extension even extension may be mandatory. The second problem is where to put the first brace. Before the dot or not. I suggest to use parenthesis like this: "path/to/archive_file.(rar|tar)", as this syntax is interpreted as alternatives in docopt. Note that pipe delimits extensions here, and not the whole placeholder content. To be honest, it's an interesting idea to use parenthesis as a tool to restrict the context where pipe is applied like "path/to/(file|directory)". Note that it's a render responsibility to recognize and transform placeholders for smth more readable and not TlDr source markup itself.

K.B.Dharun Krishna
@kbdk:matrix.org
[m]
As per @EmilySeville7cfg 's request, I have unassigned alΔΊ the issues/PRs assigned to them.
K.B.Dharun Krishna
@kbdk:matrix.org
[m]

waldyrious: Can you check this out tldr-pages/tldr-pages.github.io#65.

Thanks in advance.

1 reply
Axel Navarro
@navarroaxel
if an issue or pr is deleted by GitHub:
image.png
7 replies
This message was deleted
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Thanks
waldyrious
@waldyrious:matrix.org
[m]
I've left a comment there and also in tldr-pages/tldr#9722
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Nice, noticed it.
waldyrious
@waldyrious:matrix.org
[m]
Gotta go to sleep now πŸ˜…
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
I totally forgot you are 12 hours away lol
1 reply
waldyrious
@waldyrious:matrix.org
[m]
Thanks for not letting me drop this, K.B.Dharun Krishna !
See ya! πŸ‘‹
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Hello guys, now that GitHub supports 4 social links + 1 for website. How about we add our Twitter and fosstodon links over there? Cc navarroaxel:
7 replies
Emily Grace Seville
@EmilySeville7cfg

Hello everyone! As u already know I am working on my project namely Better TlDr (deprecated name)
or [C]ommand [L]ine [I]nterface [P]ages. For now it already solved several TlDr issues
and it's going to evolve further. Keep in mind that page render now is just a prototype
and will be completely rewritten in Go later. To be more precise the following TlDr problems
were already emilyseville7cfg-better-tldr/prototypes#10:

  • placeholders clearly indicate how much arguments they accept via syntax and syntax highlighting
  • both long and short options can be presented, no more page duplication needed πŸš€
  • placeholders for remote and local objects are supported and their syntax is unified
    (they are useful when command deals with both let's say folders and local ones)
  • several render modes available: TlDr-like and DocOpt like
    (project doesn't copy char-to-char python TlDr render output, it just make it
    to be similar)
  • etc

I invite everyone to my project. For writing tool prototypes u can use any programming
language, but for fixing mine ones you should know Bash, Sed and Awk a little bit.
Repo with prototypes is the only one where users can chose any language to use.

To be fair, this project is like a challenge for me to prove myself that I can do
what I want and change everything what I want. πŸ˜„

banana_pancakes
@banana_pancakes:matrix.org
[m]
tldr is really helpful super grateful for it and people who contribute!
banana_pancakes
@banana_pancakes:matrix.org
[m]
whats the difference/pros vs cons between the node, python, and haskel clients. out of curiousity...Ive been using Haskel...i didnt realize i was(eg: i just "apt install tldr" from Debian Stable. I didnt realize how far and deep it goes with different clients. Id like to contribute
K.B.Dharun Krishna
@kbdk:matrix.org
[m]

The Node client is our default and most recommended one with features like automatic locale detection. Whereas the python client has default Colored outputs and syntax highlighting with added flags.

I haven't used the Haskell client so I don't know about it. Our C client is similar to Python client but it is present in Fedora, Arch repos and also in Homebrew.

Almost all clients follow a strict client specification so core functionality remains the same regardless of the client you use. But some have better fetching capabilities for recent pages. Let's say I have added a page for a new command yesterday in TLDR, when I search it in Node client it automatically fetches and refreshes the local cache. But for other clients you need to do tldr -r when a page isn't present
1 reply
banana_pancakes
@banana_pancakes:matrix.org
[m]
The git repository is more than a year ahead of Debian Stable package
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Some of the community clients follow old guidelines and use the master branch so I wouldn't definitely recommend it. Feel free to use a client that supports caching and not their separate repository.
:point_up: Edit: Almost all clients follow a strict client specification so core functionality remains the same regardless of the client you use. But some have better fetching capabilities for recent pages. Let's say I have added a page for a new command yesterday in TLDR, when I search it in Node client it automatically fetches and refreshes the local cache. But for other clients you need to do tldr -u when a page isn't present
banana_pancakes
@banana_pancakes:matrix.org
[m]
Thank you its greatly appreciated! i speak for all the new people. Its a game changer
last question...
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
Sure
banana_pancakes
@banana_pancakes:matrix.org
[m]
should i apt remove an or --purge before switching...or will it integrate smoothly
K.B.Dharun Krishna
@kbdk:matrix.org
[m]
apt remove would work as it will remove the binary. Purge isn't necessary as there aren't a lot of dependencies in tldr clients so mostly nothing will be left out in remove.
banana_pancakes
@banana_pancakes:matrix.org
[m]
konpai!