Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Carl Bordum Hansen" <carl@bordum.dk>
To: <gdb-patches@sourceware.org>
Subject: [PATCH] gdb docs: do not format the ++ in C++ in man page
Date: Mon, 16 Sep 2019 21:47:00 -0000	[thread overview]
Message-ID: <BX1R9QPBILBP.3TZ1WKSD70F13@carl-T440p> (raw)

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 :-)

 gdb/doc/gdb.texinfo | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index eee0c9d4dd..68c45d9dc9 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -45056,7 +45056,7 @@ Change things in your program, so you can experiment with correcting the
 effects of one bug and go on to learn about another.
 @end itemize
 
-You can use @value{GDBN} to debug programs written in C, C@t{++}, Fortran and
+You can use @value{GDBN} to debug programs written in C, C++, Fortran and
 Modula-2.
 
 @value{GDBN} is invoked with the shell command @code{gdb}.  Once started, it reads
-- 
2.17.1


             reply	other threads:[~2019-09-16 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:47 Carl Bordum Hansen [this message]
2019-09-17  1:19 ` Simon Marchi
2019-09-17  6:02   ` Eli Zaretskii
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=BX1R9QPBILBP.3TZ1WKSD70F13@carl-T440p \
    --to=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