From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH] texi2pod.pl: import support for @t{...} from gcc
Date: Wed, 15 Jan 2020 17:59:00 -0000 [thread overview]
Message-ID: <732caf23-22a4-c843-3cea-8547d8c0f1ce@polymtl.ca> (raw)
In-Reply-To: <20190917032137.306625-1-simon.marchi@polymtl.ca>
On 2019-09-16 11:21 p.m., Simon Marchi wrote:
> GDB's man page source (in gdb.texinfo) contains:
>
> @t{++}
>
> The @t{...} part is supposed to display the wrapped text with a
> fixed-width font. The texi2pod.pl script currently doesn't handle
> @t{...}, so it appears as-is in the man page:
>
> You can use GDB to debug programs written in C, C@t{++}, Fortran and Modula-2.
>
> gcc's version of texi2pod.pl (at contrib/texi2pod.pl in gcc's repo)
> replaces @t{...} with the wrapped text as-is, which I think is an
> acceptable behavior. The fixed-width font distinction is not really
> important for a man page, where the text will be displayed with whatever
> font the user is using.
>
> Import the line that does that from gcc's version.
>
> I have verified that there is no other, unwanted change in man pages
> generated in binutils' and GDB's doc, with this patch applied.
>
> etc/ChangeLog:
>
> * texi2pod.pl: Handle @t{...} tags.
> ---
> etc/texi2pod.pl | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/etc/texi2pod.pl b/etc/texi2pod.pl
> index b0540338c8ec..8d92bcf6023b 100644
> --- a/etc/texi2pod.pl
> +++ b/etc/texi2pod.pl
> @@ -381,6 +381,7 @@ sub postprocess
> s/\@file\{([^\}]*)\}/F<$1>/g;
> s/\@w\{([^\}]*)\}/S<$1>/g;
> s/\@(?:dmn|math)\{([^\}]*)\}/$1/g;
> + s/\@t\{([^\}]*)\}/$1/g;
>
> # keep references of the form @ref{...}, print them bold
> s/\@(?:ref)\{([^\}]*)\}/B<$1>/g;
> --
> 2.23.0
>
I've pushed this patch.
Simon
prev parent reply other threads:[~2020-01-15 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 3:21 Simon Marchi
2020-01-15 17:59 ` 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=732caf23-22a4-c843-3cea-8547d8c0f1ce@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=binutils@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).