Linux-man Archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Proposed v2: revised man(7) synopsis macros
Date: Sun, 5 May 2024 16:45:54 +0200	[thread overview]
Message-ID: <Zjebo2GAgG2TK2UQ@debian> (raw)
In-Reply-To: <20240505143230.a7su5ika5gxccv5p@illithid>

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

[removed a few lists; they probably don't care]

Hi Branden,

On Sun, May 05, 2024 at 09:32:30AM -0500, G. Branden Robinson wrote:
> At 2024-05-05T16:28:23+0200, Alejandro Colomar wrote:
> > You did s/vger/lore/ and now the mail is bouncing.  :-)
> 
> Whoops.  The version of neomutt I'm using has an annoying problem; it
> won't let me group reply to tagged messages.  I haven't looked into why.
> neomutt has other annoying bugs, like cancelling MIME-related prompts if
> you backspace to the beginning of them.  There's an old saying about all
> MUAs sucking.

Heh, they do.  That's why I'm patching neomutt(1) to suck less.  :-)

Now you mention neomutt(1): I notice you don't use
$crypt_protected_headers_write.

Do you have any opinions on
<https://github.com/neomutt/neomutt/pull/4256> and
<https://github.com/neomutt/neomutt/discussions/4251>?

> 
> Possibly everyone but you on linux-man has me killfiled anyway.[1]  ;-)
> 
> Regards,
> Branden
> 
> [1] You must be >this< geriatric to get this reference.

Certainly, I'm not that geriatric.  I had to google it, but was easy.  ;)

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>
A client is hiring kernel driver, mm, and/or crypto developers;
contact me if interested.

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

  reply	other threads:[~2024-05-05 14:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  5:59 Proposed v2: revised man(7) synopsis macros G. Branden Robinson
2024-04-26  9:32 ` Alejandro Colomar
2024-05-03 20:31   ` G. Branden Robinson
2024-05-05 12:41     ` Alejandro Colomar
2024-05-05 12:44       ` Alejandro Colomar
     [not found]         ` <20240505135453.4rxsqe3so7347mli@illithid>
     [not found]           ` <ZjeTilIR86sBYrtI@debian>
2024-05-05 14:28             ` Alejandro Colomar
2024-05-05 14:32               ` G. Branden Robinson
2024-05-05 14:45                 ` Alejandro Colomar [this message]
2024-04-26 21:54 ` Lennart Jablonka
2024-04-26 22:31   ` Undeprecating man(7)'s `HP` macro? (was: Proposed v2: revised man(7) synopsis macros) G. Branden Robinson
2024-04-29  8:39 ` Proposed v2: revised man(7) synopsis macros G. Branden Robinson

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=Zjebo2GAgG2TK2UQ@debian \
    --to=alx@kernel.org \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).