From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: carl@bordum.dk, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb docs: do not format the ++ in C++ in man page
Date: Tue, 17 Sep 2019 12:36:00 -0000 [thread overview]
Message-ID: <7d725d34-8367-c875-2528-662605295645@simark.ca> (raw)
In-Reply-To: <83o8zjwjdf.fsf@gnu.org>
On 2019-09-17 2:02 a.m., Eli Zaretskii wrote:
>> Like I said on IRC, I think the best way to fix this would be to fix the texi2pod.pl
>> script to handle @t instead.
>
> I agree, but I'm also confused about the problem. If I go to that
> page, I don't see @t there, and looking at the page source reveals
> that C@t{++} has been correctly converted to C<tt>++</tt>. So I'm not
> sure why Carl sees something different.
>
> What am I missing here?
>
Hi Eli,
We are talking about the actual man page, as viewed with "man". The HTML (or info) version is rendered fine.
I can view it by doing:
1. `cd gdb/doc` in the build directory
2. `make man`
3. `man -l gdb.1`
Simon
next prev parent reply other threads:[~2019-09-17 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 21:47 Carl Bordum Hansen
2019-09-17 1:19 ` Simon Marchi
2019-09-17 6:02 ` Eli Zaretskii
2019-09-17 12:36 ` Simon Marchi [this message]
2019-09-17 12:48 ` Eli Zaretskii
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=7d725d34-8367-c875-2528-662605295645@simark.ca \
--to=simark@simark.ca \
--cc=carl@bordum.dk \
--cc=eliz@gnu.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