From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 9/9] [gdb] Fix trailing whitespace in refcard.tex
Date: Thu, 18 Jun 2026 15:38:18 +0200 [thread overview]
Message-ID: <20260618133818.55460-10-tdevries@suse.de> (raw)
In-Reply-To: <20260618133818.55460-1-tdevries@suse.de>
Fix:
...
gdb/doc/refcard.tex:314: trailing whitespace.
+b \opt{\it file\tt:}{\it line}&set breakpoint at {\it line} number \opt{in \it file}\par
gdb/doc/refcard.tex:344: trailing whitespace.
+enable \opt{{\it n}}&enable breakpoints
gdb/doc/refcard.tex:347: trailing whitespace.
+enable once \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
gdb/doc/refcard.tex:350: trailing whitespace.
+enable del \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
gdb/doc/refcard.tex:494: trailing whitespace.
+\qquad {\it command-list}&create new GDB command {\it cmd};
gdb/doc/refcard.tex:498: trailing whitespace.
+\qquad {\it help-text}&create online documentation
gdb/doc/refcard.tex:595: trailing whitespace.
+list {\it lines}&display source surrounding {\it lines},
gdb/doc/refcard.tex:629: trailing whitespace.
+statement.\cr
...
Verified by checking refcard.pdf.
---
gdb/contrib/check-whitespace-pre-commit.py | 4 +---
gdb/doc/refcard.tex | 26 +++++++++++-----------
2 files changed, 14 insertions(+), 16 deletions(-)
diff --git a/gdb/contrib/check-whitespace-pre-commit.py b/gdb/contrib/check-whitespace-pre-commit.py
index b7581a3dc70..1d23bde19a7 100755
--- a/gdb/contrib/check-whitespace-pre-commit.py
+++ b/gdb/contrib/check-whitespace-pre-commit.py
@@ -22,9 +22,7 @@ import sys
re_ignore = re.compile("ChangeLog")
# Files that are not clean, so they're only checked when changes.
-todo_list = [
- "gdb/doc/refcard.tex",
-]
+todo_list = []
clean = []
other = []
diff --git a/gdb/doc/refcard.tex b/gdb/doc/refcard.tex
index f334cce0fd0..7dfb74cfcfd 100644
--- a/gdb/doc/refcard.tex
+++ b/gdb/doc/refcard.tex
@@ -311,7 +311,7 @@ one or more arguments}
\eject
\sec Breakpoints and Watchpoints;
break \opt{\it file\tt:}{\it line}\par
-b \opt{\it file\tt:}{\it line}&set breakpoint at {\it line} number \opt{in \it file}\par
+b \opt{\it file\tt:}{\it line}&set breakpoint at {\it line} number \opt{in \it file}\par
eg:\quad{\tt break main.c:37}\quad\cr
break \opt{\it file\tt:}{\it func}&set breakpoint at {\it
func} \opt{in \it file}\cr
@@ -341,14 +341,14 @@ delete \opt{{\it n}}&delete breakpoints
disable \opt{{\it n}}&disable breakpoints
\opt{or breakpoint {\it n}}
\cr
-enable \opt{{\it n}}&enable breakpoints
+enable \opt{{\it n}}&enable breakpoints
\opt{or breakpoint {\it n}}
\cr
-enable once \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
-disable again when reached
+enable once \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
+ disable again when reached
\cr
-enable del \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
-delete when reached
+enable del \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
+ delete when reached
\cr
\cr
ignore {\it n} {\it count}&ignore breakpoint {\it n}, {\it count}
@@ -491,12 +491,12 @@ source {\it script}&read, execute GDB commands from file {\it
script}\cr
\cr
define {\it cmd}\par
-\qquad {\it command-list}&create new GDB command {\it cmd};
-execute script defined by {\it command-list}\cr
+\qquad {\it command-list}&create new GDB command {\it cmd};
+ execute script defined by {\it command-list}\cr
end&end of {\it command-list}\cr
document {\it cmd}\par
-\qquad {\it help-text}&create online documentation
-for new GDB command {\it cmd}\cr
+\qquad {\it help-text}&create online documentation
+ for new GDB command {\it cmd}\cr
end&end of {\it help-text}\cr
\endsec
@@ -592,8 +592,8 @@ show dir&show current source path\cr
\cr
list&show next ten lines of source\cr
list -&show previous ten lines\cr
-list {\it lines}&display source surrounding {\it lines},
-specified as:\cr
+list {\it lines}&display source surrounding {\it lines},
+ specified as:\cr
\quad{\opt{\it file\tt:}\it num}&line number \opt{in named file}\cr
\quad{\opt{\it file\tt:}\it function}&beginning of function \opt{in
named file}\cr
@@ -626,7 +626,7 @@ M-d&down {\it arg} frames ({\tt down})\cr
\sec GDB License;
show copying&Display GNU General Public License\cr
show warranty&There is NO WARRANTY for GDB. Display full no-warranty
-statement.\cr
+statement.\cr
\endsec
--
2.51.0
next prev parent reply other threads:[~2026-06-18 13:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 13:38 [PATCH 0/9] [gdb] More whitespace fixes Tom de Vries
2026-06-18 13:38 ` [PATCH 1/9] [gdb] Increase clean range in check-whitespace-pre-commit.py Tom de Vries
2026-06-18 13:38 ` [PATCH 2/9] [gdb] Fix leftover conflict marker in gdb/config/djgpp/README Tom de Vries
2026-06-18 13:38 ` [PATCH 3/9] [gdb] Fix new blank line at EOF in a few scripts Tom de Vries
2026-06-18 13:38 ` [PATCH 4/9] [gdb] Fix new blank line at EOF in a few xml files Tom de Vries
2026-06-18 13:38 ` [PATCH 5/9] [gdb] Ignore whitespace in imported file gdb/exc_request.defs Tom de Vries
2026-06-18 13:38 ` [PATCH 6/9] [gdb] Fix trailing whitespace in some files Tom de Vries
2026-06-18 13:38 ` [PATCH 7/9] [gdb] Ignore trailing whitespace in gdb/gdb-gdb.gdb.in Tom de Vries
2026-06-18 13:38 ` [PATCH 8/9] [gdb] Fix trailing whitespace in annotate.texinfo Tom de Vries
2026-06-18 13:38 ` Tom de Vries [this message]
2026-06-18 14:03 ` [PATCH 0/9] [gdb] More whitespace fixes Eli Zaretskii
2026-06-18 15:25 ` Tom de Vries
2026-06-18 17:13 ` Tom Tromey
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=20260618133818.55460-10-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