4 replies
But I see a lot of them are on the French pages, so not sure if I should be conscious of the language before applying the change. (i.e. if in certain languages the space is required)
Hello. My name is Philip. I just got my hands on tldr recently, and it colors conflicts with my current theme. I want to open an issues, but I saw many previous similar ones talking about client (node, python, ...), and I am not sure which one am I using.
fyi, I use windows subsystem for linux, Ubutu specifically, and I install tldr through sudo apt install tldr. So I am not sure what client am I using and what should I do about this color theme thing
7 replies
Some of our collaborators do not have 2FA and GitHub gives the option of requiring it.
I have no strong opinions on it and if we think its unnecessary then no problem.
It seems unreasonable to have the repo with nearly 40k stars without 2FA.
There's actually 2 suggestions on one of my PRs.
Would anyone care to drop their opinion on both (other than the people that made the original suggestion) just to have a 3rd opinion?
If someone else agrees, I'll just go with it and commit the suggestion.
I just claimed this https://aur.archlinux.org/packages/tldr-git and updated it but can't understand why it even points to https://github.com/tldr-pages/tldr-cpp-client which is a redirect.
From t he commits on the repo I can see that there once was C++ but now C. What prompted the change?
4 replies
1 reply
Hello! Let's decide what syntax we prefer:
command_name {{path/to/directory{1,2,...}}}# syntax highlighting is broken for this one in the official Python clientcommand_name {{path/to/directory1 path/to/directory2 ...}}# may be very longcommand_name {{path/to/directory1 ...}}
Personally I don't want to stick to brace expansion syntax because not all shells support it.
3 replies
Hello! Let's decide what syntax we prefer:
command_name {{path/to/directory{1,2,...}}}# syntax highlighting is broken for this one in the official Python clientcommand_name {{path/to/directory1 path/to/directory2 ...}}# may be very longcommand_name {{path/to/directory1 ...}}Personally I don't want to stick to brace expansion syntax because not all shells support it.
The second option is specified in the contributing guide. The python client isn't broken.
https://github.com/tldr-pages/tldr/blob/main/contributing-guides/style-guide.md#special-cases
Regarding the two factor authentication message I left above, I have message the collaborators who didn't have 2FA enabled and with some success I have managed to remove 3 people off of the list.
Could we enable it, then immediately invite anyone who is affected by the change, most of which haven't committed anything in at least 6 months.
From my understanding, the users will be given an email notice about being removed, then if we send the invites again they will require having 2FA before rejoining, then no damage is done and no-one is lost from the project since they have an invite regardless.
Is there any reason not to do this change?
Links for anyone who has access:
https://github.com/orgs/tldr-pages/outside-collaborators?query=two-factor%3Adisabled
https://github.com/organizations/tldr-pages/settings/security
5 replies
Hi everyone,
I am going to take a small break from TLDR since I have been getting a little burnt out, primarily because of the repetitive nature.
I still plan on contributing, however I won't be doing as much as I currently do, which is still not what I used to do anyway. Regardless, still ping me whenever you need another opinion and I may get back.
1 reply
2 replies
1 reply
3 months ago, an edit was made to bro pages and the repo was archived.
Just a heads-up in case people here didn't know yet as we have an open issue related to it and it's mentioned on our README under related projects.
Also dropping a note here:
tldr-pages/tldr#266