From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: ludo@gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH, doc RFA] Add guile gdb parameter support
Date: Mon, 02 Jun 2014 15:41:00 -0000 [thread overview]
Message-ID: <83vbsj9v5h.fsf@gnu.org> (raw)
In-Reply-To: <m3r438dmwu.fsf@sspiff.org>
> From: Doug Evans <xdje42@gmail.com>
> Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
> Date: Sun, 01 Jun 2014 20:13:05 -0700
>
> +@tindex Parameter
> +You can implement new @value{GDBN} parameters using Guile. A new
> +parameter is defined with the @code{make-parameter} Guile function,
> +and added to @value{GDBN} with the @code{register-parameter!} Guile function.
> +This two-step approach is taken to separate out the side-effect of adding
> +the command to @value{GDBN} from @code{make-parameter}.
^^^^^^^^^^^
Copy-paste error. Or maybe you meant the "set PARAMETER" command?
> +This function must return a string to be displayed to the user,
> +without any trailing newline.
I guess what you want to say is that GDB will add a newline, not that
the string must not end with a newline.
Otherwise, OK. Thanks.
next prev parent reply other threads:[~2014-06-02 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 19:41 Doug Evans
2014-05-22 15:46 ` Eli Zaretskii
2014-05-26 22:03 ` Ludovic Courtès
2014-05-26 22:23 ` Doug Evans
2014-05-27 7:01 ` Ludovic Courtès
2014-05-27 8:51 ` Ludovic Courtès
2014-05-27 14:43 ` Doug Evans
2014-06-02 3:13 ` Doug Evans
2014-06-02 8:31 ` Ludovic Courtès
2014-06-02 15:21 ` Doug Evans
2014-06-02 20:50 ` Ludovic Courtès
2014-06-02 15:41 ` Eli Zaretskii [this message]
2014-06-03 9:02 ` Doug Evans
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=83vbsj9v5h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=xdje42@gmail.com \
/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).