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

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

[G. Branden Robinson]

[-- Attachment #1.1: Type: text/plain, Size: 1741 bytes --]

* 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).
* 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".

See linux-man@ list discussion at
<https://lore.kernel.org/linux-man/\
20210729115508.pt6btsqd7g5tuhg6@localhost.localdomain/> and follow-ups.
---
 man7/man-pages.7 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man7/man-pages.7 b/man7/man-pages.7
index 3819dfd97..06dc7097c 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -686,14 +686,14 @@ man 7 man\-pages
 If the command is short, then it can be included inline in the text,
 in italic format, for example,
 .IR "man 7 man-pages" .
-In this case, it may be worth using nonbreaking spaces
-("\e\ ") at suitable places in the command.
+In this case, it may be worth using non-breaking spaces
+(\e\(ti) at suitable places in the command.
 Command options should be written in italics (e.g.,
 .IR \-l ).
 .PP
 Expressions, if not written on a separate indented line, should
 be specified in italics.
-Again, the use of nonbreaking spaces may be appropriate
+Again, the use of non-breaking spaces may be appropriate
 if the expression is inlined with normal text.
 .PP
 When showing example shell sessions, user input should be formatted in bold, for example
-- 
2.20.1


[-- Attachment #1.2: 0002-man-pages.7-Update-non-breaking-space-advice.patch --]
[-- Type: text/x-diff, Size: 1983 bytes --]

From 302aa3a0f2e5f0c3e9188936d4b0a25761ff5fd7 Mon Sep 17 00:00:00 2001
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Date: Sat, 31 Jul 2021 13:30:58 +1000
Subject: [PATCH 2/2] man-pages.7: Update non-breaking space advice.

* 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).
* 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".

See linux-man@ list discussion at
<https://lore.kernel.org/linux-man/\
20210729115508.pt6btsqd7g5tuhg6@localhost.localdomain/> and follow-ups.
---
 man7/man-pages.7 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man7/man-pages.7 b/man7/man-pages.7
index 3819dfd97..06dc7097c 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -686,14 +686,14 @@ man 7 man\-pages
 If the command is short, then it can be included inline in the text,
 in italic format, for example,
 .IR "man 7 man-pages" .
-In this case, it may be worth using nonbreaking spaces
-("\e\ ") at suitable places in the command.
+In this case, it may be worth using non-breaking spaces
+(\e\(ti) at suitable places in the command.
 Command options should be written in italics (e.g.,
 .IR \-l ).
 .PP
 Expressions, if not written on a separate indented line, should
 be specified in italics.
-Again, the use of nonbreaking spaces may be appropriate
+Again, the use of non-breaking spaces may be appropriate
 if the expression is inlined with normal text.
 .PP
 When showing example shell sessions, user input should be formatted in bold, for example
-- 
2.20.1


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Alejandro Colomar (man-pages)]

Hi Branden,

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!

> * 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
        The  general tendency in modern English is not to hyphenate
        after prefixes such as "multi", "non", "pre", "re",  "sub",
        and  so on.  Manual pages should generally follow this rule
        when these prefixes are used in natural  English  construc‐
        tions  with simple suffixes.  The following list gives some
        examples of the preferred forms:

            interprocess
            multithreaded
            multiprocess
            nonblocking
            nondefault
            nonempty
            noninteractive
            nonnegative
            nonportable
            nonzero
            preallocated
            precreate
            prerecorded
            reestablished
            reinitialize
            rearm
            reread
            subcomponent
            subdirectory
            subsystem

        Hyphens should be retained when the prefixes  are  used  in
        nonstandard  English  words, with trademarks, proper nouns,
        acronyms, or compound terms.  Some examples:

            non‐ASCII
            non‐English
            non‐NULL
            non‐real‐time

        Finally, note that "re‐create" and "recreate" are two  dif‐
        ferent verbs, and the former is probably what you want.


> 
> See linux-man@ list discussion at
> <https://lore.kernel.org/linux-man/\
> 20210729115508.pt6btsqd7g5tuhg6@localhost.localdomain/> and follow-ups.
> ---

BTW, this one also doesn't apply.  I think it is probably your mailer.
Can you use git-send-email(1)?

Thanks,

Alex

>   man7/man-pages.7 | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man7/man-pages.7 b/man7/man-pages.7
> index 3819dfd97..06dc7097c 100644
> --- a/man7/man-pages.7
> +++ b/man7/man-pages.7
> @@ -686,14 +686,14 @@ man 7 man\-pages
>   If the command is short, then it can be included inline in the text,
>   in italic format, for example,
>   .IR "man 7 man-pages" .
> -In this case, it may be worth using nonbreaking spaces
> -("\e\ ") at suitable places in the command.
> +In this case, it may be worth using non-breaking spaces
> +(\e\(ti) at suitable places in the command.
>   Command options should be written in italics (e.g.,
>   .IR \-l ).
>   .PP
>   Expressions, if not written on a separate indented line, should
>   be specified in italics.
> -Again, the use of nonbreaking spaces may be appropriate
> +Again, the use of non-breaking spaces may be appropriate
>   if the expression is inlined with normal text.
>   .PP
>   When showing example shell sessions, user input should be formatted in bold, for example
> 


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

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

[G. Branden Robinson]

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Alejandro Colomar (man-pages)]

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/

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

[G. Branden Robinson]

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

At 2021-08-01T12:49:39+0200, Alejandro Colomar (man-pages) wrote:
> $ 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.

Evidently!  Good grief, why is that split off?  <grumble>

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

Yup, it was more like I did not even imagine that the package had been
split up like that.  I thought there must be a licensing problem or
something.

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

Damn.  I really like GPG-signing my outbound mails, especially including
patches.  I try to exemplify the audit trails I advocate.

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

Thanks!  Without some NeoMutt help, it looks like this is my route
forward.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Alejandro Colomar (man-pages)]

Hi, Branden,

On 8/1/21 1:41 PM, G. Branden Robinson wrote:
> At 2021-08-01T12:49:39+0200, Alejandro Colomar (man-pages) wrote:
>> $ 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.
> 
> Evidently!  Good grief, why is that split off?  <grumble>
> 
>> apt-cache also helps if you don't know the exact name of the
>> git-send-email file:
> 
> Yup, it was more like I did not even imagine that the package had been
> split up like that.  I thought there must be a licensing problem or
> something.

The same happened to me the first time.

I guess it's the way Debian folks do their packaging, breaking 
semantically :) every package into smaller packages.  As send-email 
isn't needed at all for (basic) git usage, it can go into a separate 
package.

I like it.  It reduces the size of every package, and you have more 
control over what you have installed on your system.

Comparing that to the short time that I used Manjaro (Arch-based), where 
I had to install full-blown GUI programs just to get a C library...

> 
>>> 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.
> 
> Damn.  I really like GPG-signing my outbound mails, especially including
> patches.  I try to exemplify the audit trails I advocate.
> 
>> [sendemail]
>> 	smtpuser = alx.manpages
>> 	smtpserver = smtp.googlemail.com
>> 	smtpencryption = tls
>> 	smtpserverport = 587
>> 	smtpPass = my_password_goes_here
> 
> Thanks!  Without some NeoMutt help, it looks like this is my route
> forward.

If you get it to work while still signing your emails, I'd be interested 
in knowing how you have set it up.

:)


Cheers,

Alex


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

NeoMutt + GMail signed patches (was Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.)

[Alejandro Colomar (man-pages)]

Hi, Branden!

On 8/1/21 1:41 PM, G. Branden Robinson wrote:
> At 2021-08-01T12:49:39+0200, Alejandro Colomar (man-pages) wrote:
>> $ 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.
> 
> Evidently!  Good grief, why is that split off?  <grumble>
> 
>> apt-cache also helps if you don't know the exact name of the
>> git-send-email file:
> 
> Yup, it was more like I did not even imagine that the package had been
> split up like that.  I thought there must be a licensing problem or
> something.
> 
>>> 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.
> 
> Damn.  I really like GPG-signing my outbound mails, especially including
> patches.  I try to exemplify the audit trails I advocate.
> 
>> [sendemail]
>> 	smtpuser = alx.manpages
>> 	smtpserver = smtp.googlemail.com
>> 	smtpencryption = tls
>> 	smtpserverport = 587
>> 	smtpPass = my_password_goes_here
> 
> Thanks!  Without some NeoMutt help, it looks like this is my route
> forward.

I found that Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
also sends signed patches,
and digging through the source of an email,
I found she also uses NeoMutt + GMail.
But her patches always apply.
Maybe this email source gives you enough information:

Cheers,

Alex

-------
Delivered-To: alx.manpages@gmail.com
Received: by 2002:a05:6102:53c:0:0:0:0 with SMTP id m28csp2064687vsa;
         Mon, 2 Aug 2021 15:35:11 -0700 (PDT)
X-Google-Smtp-Source: 
ABdhPJzzp4BPGrUXLCFbVR76cNA983bLz0XEWDh3+8xeCEXGInQFkTYlh6sru4RZm5tPjP7yV910
X-Received: by 2002:a7b:c255:: with SMTP id 
b21mr19141206wmj.100.1627943711365;
         Mon, 02 Aug 2021 15:35:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1627943711; cv=none;
         d=google.com; s=arc-20160816;
 
b=sI3QtABQzh6Q/ebHlqUhFzVQRqhtovP1KerNKhAi88rreauKhQ82tX+u3XsOuI9f+b
 
imIU7NmQb37hZ5Hlvp8hDQy3pLYD0i7k2NAndBr1jD/s4QQbkZZMi21XVEL/yAns9fHj
 
IlU1WeXyRbL3cR6d4uCw9PBu+Gv5jzooFlhMDYg/D6HcSHHlxi0JZGwpTtTbLSCSsEiP
 
jjUFkCxYgl+RHdOa1k/djY4l6131wO4O1SY3+qF0a8w49vmhFFFUFsCYGkmn377cgvH0
 
XaDypxmlgxZufbzFh3/utJAQiFqs0V2fY2qxxS+XNES7x8S6vgHysGmDj6HGLcAQsebG
          o4CQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; 
d=google.com; s=arc-20160816;
         h=user-agent:content-disposition:mime-version:message-id:subject:cc
          :to:from:date:dkim-signature;
         bh=WuOhiOrPlib59ycfLhtU1h0LvE6Dt2vv9eCEDOmlIYw=;
 
b=OgNxknkgJhCLOra7a9getzOki39k3KHAra3edRdGH52Rq0eJDQRIdRRPS7D2MQCkhF
 
oyQ3hgtw7MP/6U7kxgvpA3YkC0ENvcxOYUrXf8Kv+zOqhePW3GftN3W3f9LjwCG1uadv
 
dc1Qs71wBnP0EAaOzli2htupKcXAsjdZArCuph+GWL7yK9lmjBAvVZaOs6ZhdSeySBA2
 
DG721R9+b0E4b7OMjRxjakI7P0+ZVnoZbD8dRBgv9I4kQRn1IophlPkghWHdk15yTaV5
 
LeDA6eO06YyPVXfLnkmqKPfl3LSrKXwgtzqz3nuNj7lkViB6lBV/n4DCnbLTmMAVMea4
          BYUw==
ARC-Authentication-Results: i=1; mx.google.com;
        dkim=pass header.i=@nabijaczleweli.xyz header.s=202006 
header.b=CbAIkxCc;
        spf=pass (google.com: domain of 
nabijaczleweli@nabijaczleweli.xyz designates 139.28.40.42 as permitted 
sender) smtp.mailfrom=nabijaczleweli@nabijaczleweli.xyz;
        dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nabijaczleweli.xyz
Return-Path: <nabijaczleweli@nabijaczleweli.xyz>
Received: from tarta.nabijaczleweli.xyz ([139.28.40.42])
         by mx.google.com with ESMTP id 
a28si11597036wrc.570.2021.08.02.15.35.10
         for <alx.manpages@gmail.com>;
         Mon, 02 Aug 2021 15:35:11 -0700 (PDT)
Received-SPF: pass (google.com: domain of 
nabijaczleweli@nabijaczleweli.xyz designates 139.28.40.42 as permitted 
sender) client-ip=139.28.40.42;
Authentication-Results: mx.google.com;
        dkim=pass header.i=@nabijaczleweli.xyz header.s=202006 
header.b=CbAIkxCc;
        spf=pass (google.com: domain of 
nabijaczleweli@nabijaczleweli.xyz designates 139.28.40.42 as permitted 
sender) smtp.mailfrom=nabijaczleweli@nabijaczleweli.xyz;
        dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nabijaczleweli.xyz
Received: from tarta.nabijaczleweli.xyz (unknown [192.168.1.250])
	by tarta.nabijaczleweli.xyz (Postfix) with ESMTPSA id 71F193602F7;
	Tue,  3 Aug 2021 00:35:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nabijaczleweli.xyz;
	s=202006; t=1627943710;
	bh=WuOhiOrPlib59ycfLhtU1h0LvE6Dt2vv9eCEDOmlIYw=;
	h=Date:From:To:Cc:Subject:From;
	b=CbAIkxCcGiriaw3R5lAXTOd1q9sSjsRNQAUeweWUKCrt2RXaIl1SN5vE+ohE+KYSY
	 I58bYVZOnoCAxZkZQD2diiSJ9dEjMcoghAgE+ac0M3Pf/u5UNZJjyl+msj3KOgJ55/
	 TPBA771poNxsrA79xnSbIUWbwq01QpfslXIXm4PnexVOgbSCWzXZbxKwnwPoLRNa4E
	 /m+70Yf5zpMbxCn1Dndt+0+Mab0zCmmzUob7NOpTthGAWFX/FNgxwIBtmroe+sskez
	 aQArzK67FpOSYxmngCyVFWdyE3TIwzY+tET509tCKWhnyCCqov2naAfCDXKWGxkf++
	 YD+Oe8AAqmRtw==
Date: Tue, 3 Aug 2021 00:35:09 +0200
From: =?utf-8?B?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH] regex.3: ffix
Message-ID: <20210802223509.ep7fzsm5un7p27aq@tarta.nabijaczleweli.xyz>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="d3akbsoizxd7rdio"
Content-Disposition: inline
User-Agent: NeoMutt/20210205


--d3akbsoizxd7rdio
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

"address of regcomp() initialized buffer" ->
"address of regcomp()-initialized buffer"

Signed-off-by: Ahelenia Ziemia=C5=84ska <nabijaczleweli@nabijaczleweli.xyz>
---
  man3/regex.3 | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man3/regex.3 b/man3/regex.3
index b6a83271c..368f48d78 100644
--- a/man3/regex.3
+++ b/man3/regex.3
@@ -66,8 +66,8 @@ All regular expression searching must be done via a compi=
led pattern
  buffer, thus
  .BR regexec ()
  must always be supplied with the address of a
-.BR regcomp ()
-initialized pattern buffer.
+.BR regcomp ()-initialized
+pattern buffer.
  .PP
  .I cflags
  is the
--=20
2.20.1

--d3akbsoizxd7rdio
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEfWlHToQCjFzAxEFjvP0LAY0mWPEFAmEIcxwACgkQvP0LAY0m
WPHV4BAAkm8MBi/6asJsCuTcaqTR3eMe7St0Zw0pd2ZlFwbZzWUkJWfMlUlWj/Xk
JOzQJ2XMpWgWyqTgFkP/HzVjYqSspqdRBcn4gsbTPBQsNNvucx0GwtLBi+BSksGs
re1B05OrwLlmExQC0H8owJ40mv92igmPpzboSV9mUp4vnMz0dKzd2XgqRAm6uijN
hM38b862cyaJj1yWqKHqkNMWCIApbV2PtIJUVQEFKmzDFRBUQqqGqUII4saLoNBn
O2psVPo3jyH9gjsQg81kozaRQXhczCTE6FzfLmYtESRTVVGmkha++YD4jevgE8a3
EOcT2O7lwPldIHqWbokgV1wlmKXKNRPuOD1SN0eMRRfVjMKr/Mih4+8cI0ezNBq4
P867DEzuCHMIEL6e33P9wmjU9D3KWFm9RuVPN+xu9pwNZMoXvW+Y8W7a2u9syqju
r7sz1nvOOYppPVqyuAvTxU7r0lfEwmwuP3LKTerAfBJP0yVjS4pLWKa5pSxE3oxh
33g+jipT3nYAJzQQS7hcmAHNhCeLG66E5FzVbHLVwT2FuKfz8OsyG2NRL+YrSuwq
D+HDculjFo26yR2XxxVOlYu/yrKIQVkj+FYdgv7DSFV7O2IUG6ZteySLFOvAwEic
H5yeSOADGL6TU46M0b8msCBssm/V3l2oSF+hz280vkvMtC5Itrk=
=1EG3
-----END PGP SIGNATURE-----

--d3akbsoizxd7rdio--

Re: NeoMutt + GMail signed patches (was Re: [PATCH 2/2] man-pages.7: Update non-breaking space advice.)

[наб]

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

On Tue, Aug 03, 2021 at 09:36:14AM +0200, Alejandro Colomar (man-pages) wrote:
> I found that Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> also sends signed patches,

FWIW, there isn't much of a trick to it, all I do is have
	[format]
		headers = "X-Mutt-PGP: OS\n"
in .gitconfig, then (cmdline verbatim for the patch you quoted):
	git format-patch --to='Alejandro Colomar <alx.manpages@gmail.com>' --cc='linux-man@vger.kernel.org' --stdout HEAD^ >> ~/mail/mailboxes/Drafts/messages

And just recall it in NeoMutt, the special header enables PGP OppEnc
(I used to just enable it manually for a while with <smime-menu>,
 which works, but got very old very fast).

Copying format-patch into drafts is an explicitly supported
configuration, and has been for decades (cf. git-format-patch(1),
DISCUSSION, 2nd paragraph ‒ active ia64 development dates it,
rest in peace).

> and digging through the source of an email,
> I found she also uses NeoMutt + GMail.
> But her patches always apply.

@nabijaczleweli.xyz is my local Postfix instance,
but this does also work on GMail (copying the mail from a temporary
mailbox into the drafts is a little iffy, but works);
you're seeing a lot of GMail headers because GMail received it.

> Cheers,
> Alex

Best,
наб

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[G. Branden Robinson]

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

At 2021-08-01T14:30:00+0200, Alejandro Colomar (man-pages) wrote:
> The same happened to me the first time.
> 
> I guess it's the way Debian folks do their packaging, breaking
> semantically :) every package into smaller packages.  As send-email
> isn't needed at all for (basic) git usage, it can go into a separate
> package.
> 
> I like it.  It reduces the size of every package, and you have more
> control over what you have installed on your system.
> 
> Comparing that to the short time that I used Manjaro (Arch-based),
> where I had to install full-blown GUI programs just to get a C
> library...

It's ironic that I overlooked this possibility.  I used to maintain
XFree86, a monolithic X Window System distribution, for Debian (XFree86
is a project now best known as a spectacular case of Open Source
Seppuku).  When I took over maintenance, it was already dozens of
packages, and I sliced it even finer.

But at the time it was Debian's policy to configure and provide
X11-enabled versions of software everywhere possible except under
special circumstaces involving package priority.  You could make a "no
X" alternative build and binary package if you wanted to go to the
trouble.

> > Thanks!  Without some NeoMutt help, it looks like this is my route
> > forward.
> 
> If you get it to work while still signing your emails, I'd be
> interested in knowing how you have set it up.

If I manage it, I certainly will.  Thanks!

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

[Alejandro Colomar (man-pages)]

Hey, 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.
> 
>>> * 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
> 

Ping.

Ahha! I found the original patch thread :)

Cheers,

Alex

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

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

[Alejandro Colomar (man-pages)]

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/