All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Ping^2: Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.
Date: Fri, 12 Nov 2021 21:33:33 +0100	[thread overview]
Message-ID: <852cc9b0-992b-dade-ca38-bff4440ef9ed@gmail.com> (raw)
In-Reply-To: <5e11d17e-d3d0-8b88-dd1b-209a4b136e51@gmail.com>

Hi, Branden!

Ping^2

On 10/17/21 21:53, Alejandro Colomar (man-pages) wrote:
> On 8/1/21 12:12 PM, G. Branden Robinson wrote:
>> Hi, Alex!
>>
>> At 2021-07-31T13:42:08+0200, Alejandro Colomar (man-pages) wrote:
>>> On 7/31/21 5:45 AM, G. Branden Robinson wrote:
>>>> * Advise usage of \~ escape instead of \SPACE; the former, a groff
>>>>     extension from circa 1990, has been supported by Heirloom
>>>>     Doctools troff since 2005 and by mandoc since 2019.  The
>>>>     advantage is that \~ is an _adjustable_ non-breaking space, so it
>>>>     will typeset non-jarringly both in .EX/.EE examples when filling
>>>>     is off, and in normal running text (which is filled).
>>>
>>> Thanks for the patch!
>>
>> You're welcome!  I've found no use cases for "\ " in man pages.  \~ is
>> almost always what is desired.
>>
>>>> * Say "non-breaking" instead of "nonbreaking".  These are the only
>>>>     occurrences of either in the man-pages tree, except in
>>>>     Changes.old, which uses "non-breaking".
>>>
>>> I'll do as usual and copy here an extract from man-pages(7) :) :
>>>
>>>     Hyphenation with multi, non, pre, re, sub, and so on
>>
>> Ahhh, ha.  Yes.  This is an impedance mismatch between the house styles
>> of the Linux man-pages and groff, at least as applied specifically to
>> the word "non-?breaking", which sees frequent use in discussions of
>> typesetting. >
>>> BTW, this one also doesn't apply.  I think it is probably your mailer.
>>> Can you use git-send-email(1)?
>>
>> Apparently not.  :(
>>
>> $ git send-email
>> git: 'send-email' is not a git command. See 'git --help'.
>> $ git --help -a | grep send
>>     imap-send            Send a collection of patches from stdin to an 
>> IMAP folder
>>     send-email           Send a collection of patches as emails
>>     send-pack            Push objects over Git protocol to another 
>> repository
>>
>> I did a web search and did not find any reports that NeoMutt does
>> violence to Git-formatted patches.  Perhaps it is GMail's fault?  (I use
>> its SMPTS server to send mail.)  Does someone on this list have
>> experience with this MUA and/or provider?  Is there a trick?
>>
>> This would explain my Michael despaired of my patch submissions even
>> when I kept their scopes under control.
>>
>> Regards,
>> Branden
>>

-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2021-11-12 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  3:45 [PATCH 2/2] man-pages.7: Update non-breaking space advice G. Branden Robinson
2021-07-31 11:42 ` Alejandro Colomar (man-pages)
2021-08-01 10:12   ` G. Branden Robinson
2021-08-01 10:49     ` Alejandro Colomar (man-pages)
2021-08-01 11:41       ` G. Branden Robinson
2021-08-01 12:30         ` Alejandro Colomar (man-pages)
2021-08-04  6:20           ` G. Branden Robinson
2021-08-03  7:36         ` NeoMutt + GMail signed patches (was Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.) Alejandro Colomar (man-pages)
2021-08-03  9:34           ` наб
2021-10-17 19:53     ` [PATCH 2/2] man-pages.7: Update non-breaking space advice Alejandro Colomar (man-pages)
2021-11-12 20:33       ` Alejandro Colomar (man-pages) [this message]

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=852cc9b0-992b-dade-ca38-bff4440ef9ed@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.