Closed sebastiaanspeck closed 2 months ago
Hello! I've noticed something unusual when checking this PR:
pages.de/common/cargo.md
is outdated, based on number of commands.pages.de/common/code.md
is outdated, based on the command contents itself.pages.de/common/cut.md
is outdated, based on number of commands.pages.es/common/audacious.md
is outdated, based on number of commands.pages.es/common/az-group.md
is outdated, based on the command contents itself.pages.es/common/cargo.md
is outdated, based on the command contents itself.pages.es/common/code.md
is outdated, based on the command contents itself.pages.es/common/cut.md
is outdated, based on number of commands.pages.fr/common/cargo.md
is outdated, based on number of commands.pages.fr/common/code.md
is outdated, based on the command contents itself.pages.hi/common/neofetch.md
is outdated, based on the command contents itself.pages.it/common/cargo.md
is outdated, based on number of commands.pages.it/common/neofetch.md
is outdated, based on the command contents itself.pages.ko/common/audacious.md
is outdated, based on number of commands.pages.ko/common/cargo.md
is outdated, based on number of commands.pages.ko/common/code.md
is outdated, based on the command contents itself.pages.nl/common/cargo.md
is outdated, based on the command contents itself.pages.nl/common/cut.md
is outdated, based on the command contents itself.pages.nl/common/xzgrep.md
is outdated, based on the command contents itself.pages.pt_BR/common/cargo-add.md
is outdated, based on the command contents itself.pages.pt_BR/common/cargo.md
is outdated, based on the command contents itself.pages.pt_BR/common/code.md
is outdated, based on the command contents itself.pages.pt_BR/common/cut.md
is outdated, based on number of commands.pages.pt_BR/common/neofetch.md
is outdated, based on the command contents itself.pages.ru/common/cut.md
is outdated, based on number of commands.pages.ta/common/cargo-add.md
is outdated, based on the command contents itself.pages.ta/common/cargo.md
is outdated, based on the command contents itself.pages.zh/common/cargo-add.md
is outdated, based on the command contents itself.pages.zh/common/cargo-install.md
is outdated, based on the command contents itself.pages.zh/common/cargo.md
is outdated, based on the command contents itself.pages.zh/common/duf.md
is outdated, based on the command contents itself.Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.
Hello! I've noticed something unusual when checking this PR:
pages.de/common/cargo.md
is outdated, based on number of commands.pages.de/common/cut.md
is outdated, based on number of commands.pages.es/common/audacious.md
is outdated, based on number of commands.pages.es/common/cut.md
is outdated, based on number of commands.pages.fr/common/cargo.md
is outdated, based on number of commands.pages.it/common/cargo.md
is outdated, based on number of commands.pages.ko/common/audacious.md
is outdated, based on number of commands.pages.ko/common/cargo.md
is outdated, based on number of commands.pages.pt_BR/common/cut.md
is outdated, based on number of commands.pages.ru/common/cut.md
is outdated, based on number of commands.Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.
Any rationale for this?
Any rationale for this?
This PR seems to be similar to #13030, I believe Sebastiaan is trying to move the --
symbols inside the placeholder so that they don't have a different color/style. I too am not sure if this is necessary (we enclose the symbols inside the placeholder if we are showing both long and short options).
The rationale for this is indeed to show the complete placeholder with the same color/styling, instead of showing --
with a different style from the actual option.
Hmm I don't know, I have mixed feels about this.
This style is more consistent with {{-short-option|--long-option}}
.
In the other hand, the coloring indicates the only value that can be changed for this placeholder, to properly follow this example, is the actual word(s).
Also, maybe it can clutter a bit the example if, for example, a considerable number of long options is in the same placeholder?
Hmm I don't know, I have mixed feels about this.
This style is more consistent with
{{-short-option|--long-option}}
.In the other hand, the coloring indicates the only value that can be changed for this placeholder, to properly follow this example, is the actual word(s).
Also, maybe it can clutter a bit the example if, for example, a considerable number of long options is in the same placeholder?
What about {{--option1|--option2}}
?
Hello! I've noticed something unusual when checking this PR:
pages.de/common/cargo.md
is outdated, based on number of commands.pages.de/common/cut.md
is outdated, based on number of commands.pages.es/common/audacious.md
is outdated, based on number of commands.pages.es/common/cut.md
is outdated, based on number of commands.pages.fr/common/cargo.md
is outdated, based on number of commands.pages.it/common/cargo.md
is outdated, based on number of commands.pages.ko/common/audacious.md
is outdated, based on number of commands.pages.ko/common/cargo.md
is outdated, based on number of commands.pages.pt_BR/common/cut.md
is outdated, based on number of commands.pages.ru/common/cut.md
is outdated, based on number of commands.Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.
In the other hand, the coloring indicates the only value that can be changed for this placeholder, to properly follow this example, is the actual word(s).
Which is why, in my opinion, the two correct ways to write it are --{{a|b}}
and {{--a|--b}}
.
I personally like the first one better.
It would be good to document this in the style guide
common
,linux
,osx
,windows
,sunos
,android
, etc.