Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.

["Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>]

Hi, Branden!

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.

Agreed.

> 
>>> * 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

$ apt-file find git-send-email
git-doc: /usr/share/doc/git-doc/git-send-email.html
git-doc: /usr/share/doc/git-doc/git-send-email.txt
git-email: /usr/lib/git-core/git-send-email
git-email: /usr/share/man/man1/git-send-email.1.gz


You should install git-email if you're on Debian.

apt-cache also helps if you don't know the exact name of the 
git-send-email file:


user@sqli:~$ apt-cache search git email | grep -e git -e email | grep -v 
github
git-email - fast, scalable, distributed revision control system (email 
add-on)
git-notifier - git commit email notification script
git-publish - git command to prepare and store patch revisions as git tags
ruby-email-reply-parser - Small library to parse plain text email content
svn-all-fast-export - fast-import based converter to convert repos from 
Subversion to git



> 
> 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?

I also use gmail, so their servers shouldn't cause any errors, I guess. 
  But I'm no expert on emailing.


[sendemail]
	smtpuser = alx.manpages
	smtpserver = smtp.googlemail.com
	smtpencryption = tls
	smtpserverport = 587
	smtpPass = my_password_goes_here


> 
> This would explain my Michael despaired of my patch submissions even
> when I kept their scopes under control.
> 

Cheers,

Alex


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