* [PATCH] gdb/doc: add '@:' after 'e.g.' to help texinfo
@ 2021-05-21 15:31 Andrew Burgess
2021-05-21 16:00 ` Eli Zaretskii
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Burgess @ 2021-05-21 15:31 UTC (permalink / raw)
To: gdb-patches
Add '@:' after 'e.g.' to let texinfo know that this is not the end of
a sentence. This is only needed when there's a space immediately
after the last '.'.
gdb/doc/ChangeLog:
* gdb.texi (Initialization Files): Add '@:' after 'e.g.'.
(Source Path): Likewise.
(GDB/MI Development and Front Ends): Likewise.
(ARM Features): Likewise.
(gdb man): Likewise.
---
gdb/doc/ChangeLog | 8 ++++++++
gdb/doc/gdb.texinfo | 10 +++++-----
2 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 56f37eb2288..90d827a50e7 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -1438,7 +1438,7 @@
As the system wide and home directory initialization files are
processed before most command line options, changes to settings
-(e.g. @samp{set complaints}) can affect subsequent processing of
+(e.g.@: @samp{set complaints}) can affect subsequent processing of
command line options and operands.
The following sections describe where @value{GDBN} looks for the early
@@ -9414,7 +9414,7 @@
would be similar.
When searching for source files on MS-DOS and MS-Windows, where
-absolute paths start with a drive letter (e.g.
+absolute paths start with a drive letter (e.g.@:
@file{C:/project/foo.c}), @value{GDBN} will remove the drive letter
from the file name before appending it to a search directory from
@dfn{source path}; for instance if the executable references the
@@ -29656,7 +29656,7 @@
Since @code{--interpreter=mi} always points to the latest MI version, it is
recommended that front ends request a specific version of MI when launching
-@value{GDBN} (e.g. @code{--interpreter=mi2}) to make sure they get an
+@value{GDBN} (e.g.@: @code{--interpreter=mi2}) to make sure they get an
interpreter with the MI version they expect.
The following table gives a summary of the released versions of the MI
@@ -45987,7 +45987,7 @@
It should contain registers @samp{r0} through @samp{r13}, @samp{sp},
@samp{lr}, @samp{pc}, and @samp{cpsr}.
-For M-profile targets (e.g. Cortex-M3), the @samp{org.gnu.gdb.arm.core}
+For M-profile targets (e.g.@: Cortex-M3), the @samp{org.gnu.gdb.arm.core}
feature is replaced by @samp{org.gnu.gdb.arm.m-profile}. It should contain
registers @samp{r0} through @samp{r13}, @samp{sp}, @samp{lr}, @samp{pc},
and @samp{xpsr}.
@@ -46935,7 +46935,7 @@
Display the value of an expression.
@item c
-Continue running your program (after stopping, e.g. at a breakpoint).
+Continue running your program (after stopping, e.g.@: at a breakpoint).
@item next
Execute next program line (after stopping); step @emph{over} any
--
2.25.4
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] gdb/doc: add '@:' after 'e.g.' to help texinfo
2021-05-21 15:31 [PATCH] gdb/doc: add '@:' after 'e.g.' to help texinfo Andrew Burgess
@ 2021-05-21 16:00 ` Eli Zaretskii
0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2021-05-21 16:00 UTC (permalink / raw)
To: Andrew Burgess; +Cc: gdb-patches
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Fri, 21 May 2021 16:31:43 +0100
>
> Add '@:' after 'e.g.' to let texinfo know that this is not the end of
> a sentence. This is only needed when there's a space immediately
> after the last '.'.
>
> gdb/doc/ChangeLog:
>
> * gdb.texi (Initialization Files): Add '@:' after 'e.g.'.
> (Source Path): Likewise.
> (GDB/MI Development and Front Ends): Likewise.
> (ARM Features): Likewise.
> (gdb man): Likewise.
Thanks, this is OK.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-05-21 16:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-21 15:31 [PATCH] gdb/doc: add '@:' after 'e.g.' to help texinfo Andrew Burgess
2021-05-21 16:00 ` Eli Zaretskii
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).