From: Eli Zaretskii <eliz@gnu.org>
To: tromey@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [review] Document and extend readline-bindable functions
Date: Sat, 09 Nov 2019 20:03:00 -0000 [thread overview]
Message-ID: <83d0e095sf.fsf@gnu.org> (raw)
In-Reply-To: <gerrit.1573325825000.I2233779b7aefe372f19bd03c8f325733c3385e72@gnutoolchain-gerrit.osci.io>
> Date: Sat, 9 Nov 2019 13:57:06 -0500
> From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
>
> Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/603
> ......................................................................
>
> Document and extend readline-bindable functions
>
> This adds readline-bindable function names to a few gdb functions that
> already had key bindings. This lets users change the bindings.
>
> This also removes the gdb-command function. Due to how this function
> is implemented, it doesn't make sense to allow binding it.
>
> Finally, this updates the documentation to reflect these changes.
>
> gdb/ChangeLog
> 2019-11-09 Tom Tromey <tom@tromey.com>
>
> * tui/tui.c (tui_initialize_readline): Add new bindable readline
> functions.
>
> gdb/doc/ChangeLog
> 2019-11-09 Tom Tromey <tom@tromey.com>
>
> * gdb.texinfo (TUI Keys): Document readline function names.
OK for the documentation part, thanks.
next prev parent reply other threads:[~2019-11-09 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 18:57 Tom Tromey (Code Review)
2019-11-09 20:03 ` Eli Zaretskii [this message]
2019-11-11 23:57 ` Tom Tromey (Code Review)
2019-11-12 0:01 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-12 0:01 ` Sourceware to Gerrit sync (Code Review)
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=83d0e095sf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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