From: Ingo Schwarze <email@example.com> To: firstname.lastname@example.org, email@example.com Subject: Re: Spurious space in demandoc.1 Date: Sun, 20 Mar 2022 17:00:31 +0100 [thread overview] Message-ID: <YjdPn3zr1yrOiitu@asta-kit.de> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Paul, Paul A. Patience wrote on Sun, Mar 13, 2022 at 01:20:37AM +0000: > I found a typo in demandoc.1. > Not sure if it's worth a commit all by itself. Yes it would, even small bugs are worth fixing, and there is no benefit to letting bugfix patches accumulate before committing. However, the whole sentence is misplaced, meaningless, and confusing in this manual page, so i just deleted the whole line outright, see the committed patch below. While here, please note that the whole demandoc(1) program is kind of an anachronism. You are usually better off using "mandoc FILE | col -b" instead because demandoc(1) soemtimes deletes too much from the output stream. Multiple times, i felt tempted to delete the whole demandoc(1) program from the mandoc toolbox without any replacement. The only reason i didn't delete it yet is that i'm not completely sure what people use it for, how they use it, and why. Myself, i certainly do not use it and hardly bother maintaining it unless compilation breaks. Then again, i absolutely never use spell checking programs, and when they are built in to other software, i completely disable all spell checking features wherever i can. *If* demandoc(1) has any merit in the context of spell checking (or in any other area) then rather than deleting it outright, it would be better to clean up and improve the required features and include them in the mandoc(1) program itself. So demandoc(1) will probably lurk around half-unmaintained until i understand its uses and find a tester who will explain those uses and later test patches to mandoc to support them natively instead of in a rather dirty additional program. Yours, Ingo Index: demandoc.1 =================================================================== RCS file: /home/cvs/mandoc/mandoc/demandoc.1,v retrieving revision 1.8 diff -u -r1.8 demandoc.1 --- demandoc.1 12 Sep 2014 00:10:26 -0000 1.8 +++ demandoc.1 20 Mar 2022 15:36:09 -0000 @@ -80,7 +80,6 @@ Such errors cause .Nm to exit at once, possibly in the middle of parsing or formatting a file. -The output databases are corrupt and should be removed . .El .Sh EXAMPLES The traditional usage of -- To unsubscribe send an email to email@example.com
next prev parent reply other threads:[~2022-03-20 16:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-13 1:20 Paul A. Patience 2022-03-20 16:00 ` Ingo Schwarze [this message] 2022-03-20 16:05 ` Ingo Schwarze
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=YjdPn3zr1yrOiitu@asta-kit.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Spurious space in demandoc.1' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).