From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH 01/10] fanotify_init.2: tfix
Date: Mon, 22 Aug 2022 21:02:48 +0200 [thread overview]
Message-ID: <e09eb500-d32b-1334-fff3-64803e62b11f@gmail.com> (raw)
In-Reply-To: <20220822182140.ttqdmboeuznr6qa6@jwilk.net>
[-- Attachment #1.1: Type: text/plain, Size: 1641 bytes --]
Hi Jakub,
On 8/22/22 20:21, Jakub Wilk wrote:
> * Alejandro Colomar <alx.manpages@gmail.com>, 2022-08-20 01:28:
>> BTW, I noticed you find a lot of typos. I'm curious: do you find them
>> when reading, or you run a tool that finds them?
>
> I have two unconventional spellcheckers in my toolbox:
>
> https://jwilk.net/software/mwic
> https://jwilk.net/software/anorack
>
> I usually run them on diffs, like this:
>
> $ git pull
> ...
> $ git diff @{1} | grep ^+ | mwic
> [wade through the jungle of false positives]
>
Interesting. I run both through the entire repo.
anorack(1) seems to be reasonable, in that it runs in under 1 second,
and only has 138 matches. Many of them are false positives, but it's
not unreasonable to go through them all.
$ time find man* -type f | xargs anorack | wc -l
138
real 0m0.971s
user 0m0.691s
sys 0m0.024s
I could add a `make lint-spell-anorack` target to run it from time to
time. Maybe you could special-case some of those false positives to
make it even better?
mwick(1) seems to have an unreasonably huge number of false positives:
$ time find man* -type f | xargs mwic | wc -l
139760
real 0m38.862s
user 0m38.653s
sys 0m0.224s
It seems it could get some help of understanding man(7) syntax to limit
itself to text. I'm definitely not adding this one for now.
Also, it would be nice if both of them had a way of reporting errors to
make(1) through an EXIT STATUS, which could also be documented in their
manual pages.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-22 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 19:08 [PATCH 01/10] fanotify_init.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 02/10] landlock_restrict_self.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 03/10] memfd_secret.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 04/10] clockid_t.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 05/10] dev_t.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 06/10] itimerspec.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 07/10] timespec.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 08/10] tm.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 09/10] fanotify.7: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 10/10] tcp.7: tfix Jakub Wilk
2022-08-19 23:28 ` [PATCH 01/10] fanotify_init.2: tfix Alejandro Colomar
2022-08-21 5:28 ` G. Branden Robinson
2022-08-21 11:28 ` Alejandro Colomar
2022-08-22 18:21 ` Jakub Wilk
2022-08-22 19:02 ` Alejandro Colomar [this message]
2022-08-19 23:32 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e09eb500-d32b-1334-fff3-64803e62b11f@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox