From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
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 06:02:00 -0000 [thread overview]
Message-ID: <83o8zjwjdf.fsf@gnu.org> (raw)
In-Reply-To: <d76f9c9c-bc9c-186a-6032-c1904adea0c4@simark.ca> (message from Simon Marchi on Mon, 16 Sep 2019 21:19:12 -0400)
> From: Simon Marchi <simark@simark.ca>
> Date: Mon, 16 Sep 2019 21:19:12 -0400
>
> On 2019-09-16 5:47 p.m., Carl Bordum Hansen wrote:
> > This change means that the html version of the man page does not stylize
> > the "++" in the third paragraph.
> > (https://sourceware.org/gdb/current/onlinedocs/gdb/gdb-man.html). The
> > tradeoff is, in my opinion, worth it as the man page reads better, since
> > it is now formatted properly. Before this change, it read as:
> > "... programs written in C, C@t{++}, ...".
> > ---
> >
> > Hello, this is my first patch to a GNU project ever and also the first time I
> > use an email-based git workflow, so please excuse my mistakes :-)
>
> Hi Carl,
>
> Thanks for your patches. I see you've used git-send-email, that's excellent.
>
> 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?
next prev parent reply other threads:[~2019-09-17 6:02 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 [this message]
2019-09-17 12:36 ` Simon Marchi
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=83o8zjwjdf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=carl@bordum.dk \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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