public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] texi2pod.pl: import support for @t{...} from gcc Date: Wed, 15 Jan 2020 19:14:00 -0000 [thread overview] Message-ID: <c12081a66b4abe34d2c858c78d4028606a082579@gdb-build> (raw) *** TEST RESULTS FOR COMMIT c12081a66b4abe34d2c858c78d4028606a082579 *** commit c12081a66b4abe34d2c858c78d4028606a082579 Author: Simon Marchi <simon.marchi@polymtl.ca> AuthorDate: Wed Jan 15 12:58:08 2020 -0500 Commit: Simon Marchi <simon.marchi@efficios.com> CommitDate: Wed Jan 15 12:58:09 2020 -0500 texi2pod.pl: import support for @t{...} from gcc 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. diff --git a/etc/ChangeLog b/etc/ChangeLog index 78e9366e34..8742e2afc1 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,7 @@ +2020-01-15 Simon Marchi <simon.marchi@polymtl.ca> + + * texi2pod.pl: Handle @t{...} tags. + 2018-06-19 Simon Marchi <simon.marchi@ericsson.com> * configure.in: Remove AC_PREREQ. diff --git a/etc/texi2pod.pl b/etc/texi2pod.pl index b0540338c8..8d92bcf602 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;
next reply other threads:[~2020-01-15 18:55 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-15 19:14 gdb-buildbot [this message] 2020-01-15 19:12 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot 2020-01-15 19:59 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2020-01-17 9:49 ` Failures on Fedora-i686, " gdb-buildbot 2020-01-17 10:07 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master *** BREAKAGE *** gdb-buildbot 2020-01-17 10:17 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot 2020-01-17 10:32 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2020-01-17 10:38 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m64, branch master *** BREAKAGE *** gdb-buildbot 2020-01-17 10:39 ` Failures on Fedora-x86_64-m64, branch master gdb-buildbot 2020-01-17 10:51 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2020-01-17 10:57 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
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=c12081a66b4abe34d2c858c78d4028606a082579@gdb-build \ --to=gdb-buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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).