From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb-patches@sourceware.org
Subject: [doc] Move/edit set/show extended-prompt
Date: Thu, 20 Oct 2011 15:20:00 -0000 [thread overview]
Message-ID: <m31uu7zome.fsf@redhat.com> (raw)
Tom pointed out the set/show extended-prompt section in NEWS was in the
wrong place. I moved it, and added a brief summary. I also fixed two
typos.
OK?
Cheers,
Phil
--
2011-10-20 Phil Muldoon <pmuldoon@redhat.com>
* NEWS: Move set/show extended-prompt to "New Options". Expand
description. Fix typos.
--
diff --git a/gdb/NEWS b/gdb/NEWS
index 80c59f6..3a8b28c 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -24,14 +24,12 @@
replaced it. Additionally, the default for "print-stack" is now
"off".
- ** A prompt subsitution hook (prompt_hook) is now available to the
+ ** A prompt substitution hook (prompt_hook) is now available to the
Python API.
- ** A new command set/show extended-prompt has been added.
-
** A new Python module, gdb.prompt has been added to the GDB Python
modules library. This module provides functionality for
- escape sequentions in prompts (used by set/show
+ escape sequences in prompts (used by set/show
extended-prompt). These escape sequences are replaced by their
corresponding value.
@@ -116,6 +114,14 @@ info auto-load-scripts [REGEXP]
* New options
+set extended-prompt
+show extended-prompt
+ Set the GDB prompt, and allow escape sequences to be inserted to
+ display miscellaneous information (see help set extended-prompt for
+ the list of sequences). This prompt (and any information
+ accessed through the escape sequences) is updated every time the
+ prompt is displayed.
+
set print entry-values (both|compact|default|if-needed|no|only|preferred)
show print entry-values
Set printing of frame argument values at function entry. In some cases
next reply other threads:[~2011-10-20 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 15:20 Phil Muldoon [this message]
2011-10-20 15:59 ` Eli Zaretskii
2011-10-24 12:34 ` Phil Muldoon
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=m31uu7zome.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--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