Repository navigation
Conversation
peternewman
left a comment
There was a problem hiding this comment.
Thanks for this.
Regarding the options with arguments, looking at the grep man page for example, it looks like this:
-e PATTERN, --regexp=PATTERN
It would seem sense to me to follow the same style so would you mind updating them to match
|
@peternewman PTAL |
peternewman
left a comment
There was a problem hiding this comment.
I like this new more succinct wording, but I've asked @luzpaz for a review too as they had tweaked this in the past.
|
Sorry, I have used markdown formatting while describing the FILE and LIST arguments earlier, and this is an rst file. Fixed now. |
187c37c to
eecac55
Compare
peternewman
left a comment
There was a problem hiding this comment.
Just one minor comment
|
Is there anything else I need to address here? @peternewman @luzpaz |
peternewman
left a comment
There was a problem hiding this comment.
Looks great thanks @kolyshkin . Just some minor tidying suggestions.
Also none of the actions have run for some reason so I'm going to try and close and open the PR to see if it kicks them off...
184400d to
ea9bfe3
Compare
|
Rebased; addressed review comments; PTAL @peternewman |
peternewman
left a comment
There was a problem hiding this comment.
LGTM, just one minor tweak
|
@luzpaz do you want to take a look too as you've tweaked this in the past? |
|
I am pretty sure there are many more improvements that can be done to the README in this repo. Originally my intention was to merely add Can this be merged as is (unless there are some incorrect things that this PR adds), and implement more improvements separately on top of this? PS if you want to see how this is rendered (by Github, that is), see https://github.com/kolyshkin/codespell/blob/patch-1/README.rst. |
Yeah sorry, just spotting related bits in the course or reviewing your PR.
Yes certainly. I'd like to give @luzpaz a little while to take a look, but happy to merge if they've not reviewed soon.
Yeah, I'd had a look already and it looks fine to me thanks! |
|
Thanks for the refinements. LGTM |
|
Just found this old PR which I spent so much time on and addressed every concern, yet it was not merged (probably merely forgotten). This was all manual editing in pre-AI times. Let me try to revive this. |
It took me a while to figure out how to specify a list of ignored words in a configuration file, as --ignore-words-list was missing from README (I eventually found it elsewhere). * add --ignore-words-list long option next to -L; * add ignore-words-list to the config file examples; * add argument to -S, --skip; * improve and simplify options description. [v2: make config file options order match that in cli example] [v3: more description changes as suggested by reviewers] [v4: rebase; drop changes made obsolete by upstream README rework] Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
|
Rebased onto current main. Since the README was reworked in the meantime, I redid the change on top of it. Kept:
Dropped, as made obsolete by upstream changes:
@peternewman @luzpaz PTAL |
It took me a while to figure out how to specify a list of ignored words
in a configuration file, as --ignore-words-list was missing from README
(I eventually found it elsewhere).
--ignore-words-listlong option next to-Lignore-words-listto the.codespellrcexample.codespellrcexample, made options order match that of cli example