From: Simon Marchi <simark@simark.ca>
To: Carl Bordum Hansen <carl@bordum.dk>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] etc/texi2pod.pl: C<>'s can be nested as well
Date: Tue, 17 Sep 2019 01:40:00 -0000 [thread overview]
Message-ID: <a97ef9e2-0f92-7db7-8f44-87f8d5ce822f@simark.ca> (raw)
In-Reply-To: <BX1RO04GX4C8.1F9RUUJRL3BIC@carl-T440p>
On 2019-09-16 6:06 p.m., Carl Bordum Hansen wrote:
> ---
> etc/texi2pod.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/etc/texi2pod.pl b/etc/texi2pod.pl
> index 34ba7efd0f..167cc71ba9 100644
> --- a/etc/texi2pod.pl
> +++ b/etc/texi2pod.pl
> @@ -416,9 +416,9 @@ sub postprocess
> s/</</g;
> s/>/>/g;
>
> - # Now un-nest all B<>, I<>, R<>. Theoretically we could have
> + # Now un-nest all B<>, I<>, R<>, C<>. Theoretically we could have
> # indefinitely deep nesting; in practice, one level suffices.
> - 1 while s/([BIR])<([^<>]*)([BIR])<([^<>]*)>/$1<$2>$3<$4>$1</g;
> + 1 while s/([BIRC])<([^<>]*)([BIRC])<([^<>]*)>/$1<$2>$3<$4>$1</g;
>
> # Replace R<...> with bare ...; eliminate empty markup, B<>;
> # shift white space at the ends of [BI]<...> expressions outside
>
Hi Carl,
Can you explain why this change is needed? Is there a file that was not
generated properly?
Simon
prev parent reply other threads:[~2019-09-17 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 22:06 Carl Bordum Hansen
2019-09-17 1:40 ` Simon Marchi [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=a97ef9e2-0f92-7db7-8f44-87f8d5ce822f@simark.ca \
--to=simark@simark.ca \
--cc=carl@bordum.dk \
--cc=gdb-patches@sourceware.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