From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [gdb/doc] Use '@:' after abbreviation
Date: Mon, 2 Feb 2026 15:18:46 +0100 [thread overview]
Message-ID: <20260202141846.1863170-1-tdevries@suse.de> (raw)
In gdb/doc/gdb.texinfo, we have:
...
For every type there is also a default kind associated with it, e.g.@
@code{Integer} in @value{GDBN} will internally be an @code{Integer*4} (see the
table below for default types).
...
While the @NL command [1] does probably prevent the sentence ending at 'e.g.',
the usual way to accomplish this is to use '@:' [2], so use that instead.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33868
[1] https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Multiple-Spaces.html
[2] https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Not-Ending-a-Sentence.html
---
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 80f49e21b7e..d39fa02b711 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -18131,7 +18131,7 @@ the size of each of the two @code{Real}'s it is composed of. A
@code{Complex*4} would thus consist of two @code{Real*4}s and occupy 8 bytes
of memory.
-For every type there is also a default kind associated with it, e.g.@
+For every type there is also a default kind associated with it, e.g.@:
@code{Integer} in @value{GDBN} will internally be an @code{Integer*4} (see the
table below for default types). The default types are the same as in @sc{gnu}
compilers but note, that the @sc{gnu} default types can actually be changed by
base-commit: ef7aabf7979ba4812bfa1568e072653bb8127ea8
--
2.51.0
next reply other threads:[~2026-02-02 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 14:18 Tom de Vries [this message]
2026-02-02 14:33 ` 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=20260202141846.1863170-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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