From: Bjarni Ingi Gislason <bjarniig@simnet.is>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, branden@debian.org
Subject: Re: '^\}$' is changed to a space character
Date: Thu, 2 Oct 2025 21:57:44 +0000 [thread overview]
Message-ID: <aN71WBBvfKMQjD4s@kassi.invalid.is> (raw)
In-Reply-To: <32j4rxtwivo2jafhq7fmtz4rk4kyhmv4ldzoq64757ercbiwxb@zfgmna4wiuvs>
On Wed, Oct 01, 2025 at 08:49:38AM +0200, Alejandro Colomar wrote:
> Hi Bjarni.
>
> On Tue, Sep 30, 2025 at 10:36:07PM +0000, Bjarni Ingi Gislason wrote:
> > A patch is superfluous
> >
> > sed -e '/^\\\}$/ {s/^/./}'
>
> This would also work; thanks! After all, what I need is something I can
> run to get the page changed.
>
> On the other hand, I think I prefer Branden's approach, which entirely
> eliminates the low-level roff(7) there. What do you think?
>
>
I did not get a copy of Branden's e-mail.
I suggest to get your own knowledge of the troff language,
http://troff.org/54.pdf
so that you are not addicted to the opinions of others.
next prev parent reply other threads:[~2025-10-02 21:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 18:17 '^\}$' is changed to a space character Bjarni Ingi Gislason
2025-09-30 18:46 ` Alejandro Colomar
2025-09-30 22:36 ` Bjarni Ingi Gislason
2025-10-01 6:49 ` Alejandro Colomar
2025-10-02 21:57 ` Bjarni Ingi Gislason [this message]
2025-09-30 19:40 ` G. Branden Robinson
2025-09-30 19:44 ` G. Branden Robinson
2025-10-02 22:25 ` Alejandro Colomar
2025-10-04 9:16 ` Alejandro Colomar
2025-10-04 9:42 ` G. Branden Robinson
2025-10-04 10:30 ` Alejandro Colomar
2025-10-05 13:48 ` '^\}$' is (not) " G. Branden Robinson
2025-10-05 18:47 ` Alejandro Colomar
2025-10-06 8:51 ` G. Branden Robinson
2025-10-06 10:25 ` Alejandro Colomar
2025-10-06 10:42 ` groff build problem involving "ckd_mul" and "ckd_add" G. Branden Robinson
2025-10-06 11:10 ` Alejandro Colomar
2025-10-07 2:06 ` Collin Funk
2025-10-07 8:47 ` Alejandro Colomar
2025-10-07 20:06 ` G. Branden Robinson
2025-10-07 20:24 ` Alejandro Colomar
2025-10-07 20:29 ` G. Branden Robinson
2025-10-07 21:10 ` Alejandro Colomar
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=aN71WBBvfKMQjD4s@kassi.invalid.is \
--to=bjarniig@simnet.is \
--cc=alx@kernel.org \
--cc=branden@debian.org \
--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