Vítor Henrique

Note: I'm not writing to /tmp/bad-urls.txt for Windows compability, but the user is free to change this on the script in the `main` function.

It doesn't handle it currently, sometimes I have to wait a while to run the script again but IIRC it can eventually do an entire run without being blocked if...

I think the right place for this script is in scripts/, given that its complexity increased a bit, and thus making contributions easier. This way it's possible to add another...

Thanks for adding this limit. As for the per-domain rate limit, I have an idea: splitting the links in lists, where each list contains links that belong to a specific...

Hi @vanvuvuong! I'm one of the organization members of the tldr project. I see you are interested in CLI documentation, so I think you would like [tldr](https://github.com/tldr-pages/tldr), as it is...

> > See https://github.com/tldr-pages/tldr/pull/12354#discussion_r1501872389 details on the "See command1 for function1, command2 for function2" syntax proposal. > > We should probably document this in the style guide too. Yeah, I...

@kbdharun @sebastiaanspeck @acuteenvy on second thought, I think the "See `command1` for _function1_, `command1` for _function2_" syntax is not ideal. Introducing a different syntax for suggested pages can be worse...

> What do you mean? There are no suggestions without a description in this PR. I mean, if we want to standardize the syntax you suggested in the style guide,...

> Suggesting two pages with a description and one without looks weird to me nevertheless. I'd personally avoid this and either describe all suggestions or none. I personally disagree, the...

> In this suggestion, the comma used can confuse users i.e. is command2 and command3 used for function3 or is command3 only used for function3. Yeah, I agree on that,...