sort: Move help strings to markdown file #4808
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sylvestre
reviewed
Apr 30, 2023
src/uu/sort/sort.md
Outdated
|
|
||
| ## After help | ||
|
|
||
| The key format is FIELD[.CHAR][OPTIONS][,FIELD[.CHAR]][OPTIONS]. |
There was a problem hiding this comment.
please ignore this warning
sylvestre
reviewed
Apr 30, 2023
sylvestre
reviewed
Apr 30, 2023
sylvestre
reviewed
Apr 30, 2023
src/uu/sort/sort.md
Outdated
Comment on lines
13
to
19
| Fields by default are separated by the first whitespace after a non-whitespace character. Use -t to specify a custom separator. | ||
| In the default case, whitespace is appended at the beginning of each field. Custom separators however are not included in fields. | ||
|
|
||
| FIELD and CHAR both start at 1 (i.e. they are 1-indexed). If there is no end specified after a comma, the end will be the end of the line. | ||
| If CHAR is set 0, it means the end of the field. CHAR defaults to 1 for the start position and to 0 for the end position. | ||
|
|
||
| Valid options are: MbdfhnRrV. They override the global options for this key. |
There was a problem hiding this comment.
Suggested change
| Fields by default are separated by the first whitespace after a non-whitespace character. Use -t to specify a custom separator. | |
| In the default case, whitespace is appended at the beginning of each field. Custom separators however are not included in fields. | |
| FIELD and CHAR both start at 1 (i.e. they are 1-indexed). If there is no end specified after a comma, the end will be the end of the line. | |
| If CHAR is set 0, it means the end of the field. CHAR defaults to 1 for the start position and to 0 for the end position. | |
| Valid options are: MbdfhnRrV. They override the global options for this key. | |
| Fields by default are separated by the first whitespace after a non-whitespace character. Use `-t` to specify a custom separator. | |
| In the default case, whitespace is appended at the beginning of each field. Custom separators however are not included in fields. | |
| `FIELD` and `CHAR` both start at 1 (i.e. they are 1-indexed). If there is no end specified after a comma, the end will be the end of the line. | |
| If `CHAR` is set 0, it means the end of the field. `CHAR` defaults to 1 for the start position and to 0 for the end position. | |
| Valid options are: `MbdfhnRrV`. They override the global options for this key. |
iambasanta
force-pushed
the
sort-move-help-strings-to-md-file
branch
2 times, most recently
from
822df36 to
e5a8cdc
Compare
sylvestre
reviewed
Apr 30, 2023
iambasanta
force-pushed
the
sort-move-help-strings-to-md-file
branch
from
e5a8cdc to
687bf09
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move help strings for
sortto its own markdown file.