From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: [PATCHSET] [3/4] Fix various issue in TUI
Date: Wed, 31 Dec 2014 17:50:00 -0000 [thread overview]
Message-ID: <83wq57btea.fsf@gnu.org> (raw)
This patch fixes a couple of problems with documentation of TUI
features.
OK?
2014-12-31 Eli Zaretskii <eliz@gnu.org>
* gdb/tui/tui-win.c (tui_scroll_left_command, tui_scroll_right_command):
Doc fix.
* gdb/doc/gdb.texinfo (TUI Commands): Document the possible
values of NAME argument to 'winheight' command. Explain the
effect of 'tabset' setting better.
--- gdb/tui/tui-win.c~0 2014-10-29 21:45:50 +0200
+++ gdb/tui/tui-win.c 2014-12-31 13:55:32 +0200
@@ -403,10 +403,10 @@
Scroll window backward.\n\
Usage: - [win] [n]\n"));
add_com ("<", class_tui, tui_scroll_left_command, _("\
-Scroll window forward.\n\
+Scroll window text to the left.\n\
Usage: < [win] [n]\n"));
add_com (">", class_tui, tui_scroll_right_command, _("\
-Scroll window backward.\n\
+Scroll window text to the right.\n\
Usage: > [win] [n]\n"));
if (xdb_commands)
add_com ("w", class_xdb, tui_xdb_set_win_height_command, _("\
--- gdb/doc/gdb.texinfo~0 2014-10-29 21:45:50 +0200
+++ gdb/doc/gdb.texinfo 2014-12-31 16:01:29 +0200
@@ -24384,11 +24384,15 @@
@kindex winheight
Change the height of the window @var{name} by @var{count}
lines. Positive counts increase the height, while negative counts
-decrease it.
+decrease it. The @var{name} parameter can be one of @code{src} (the
+source window), @code{cmd} (the command window), @code{asm} (the
+disassembly window), or @code{regs} (the register display window).
@item tabset @var{nchars}
@kindex tabset
-Set the width of tab stops to be @var{nchars} characters.
+Set the width of tab stops to be @var{nchars} characters. This
+setting affects the display of TAB characters in the source and
+assembly windows.
@end table
@node TUI Configuration
next reply other threads:[~2014-12-31 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 17:50 Eli Zaretskii [this message]
2015-01-05 19:29 ` Pedro Alves
2015-01-06 15:58 ` Eli Zaretskii
2015-01-06 16:20 ` Pedro Alves
2015-01-16 15:55 ` Eli Zaretskii
2015-01-16 11:35 ` 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=83wq57btea.fsf@gnu.org \
--to=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).