From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: operate-and-get-next
Date: Thu, 04 Oct 2001 00:00:00 -0000 [thread overview]
Message-ID: <8011-Thu04Oct2001090058+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <87r8skfh47.fsf@creche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: 03 Oct 2001 17:17:44 -0600
>
> Bash has a readline command called `operate-and-get-next' which I use
> very frequently (many times per day). It works like this: go up the
> history list using C-p. Then type C-o (the operate-and-get-next key).
> This acts like Enter, but when the prompt returns the next command in
> history is already available for editing. This key binding makes it
> very convenient to replay a previously-entered sequence of commands.
> I've long missed it in gdb; for some reason it is a bash-specific key
> binding and is not available in readline itself.
I was missing such a feature as well. Thanks for implementing it.
> The appended patch implements this new readline command and gives it
> the same binding in gdb that it has in bash.
I think we should mention this in the "Command Syntax" section, where
the action of RET is described.
next prev parent reply other threads:[~2001-10-04 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 16:05 Tom Tromey
2001-10-04 0:00 ` Eli Zaretskii [this message]
2001-10-04 18:16 ` Tom Tromey
2001-10-09 12:06 ` Eli Zaretskii
2001-10-09 12:48 ` Tom Tromey
2001-10-10 17:53 ` Elena Zannoni
2001-10-13 10:24 ` Tom Tromey
2001-10-15 9:13 ` Elena Zannoni
[not found] ` <878zdibdxb.fsf@creche.redhat.com>
2001-11-08 16:01 ` Elena Zannoni
2001-11-08 18:22 ` Tom Tromey
2001-11-09 13:16 ` Eli Zaretskii
[not found] <15362.64511.39505.586347@krustylu.cygnus.com>
2001-11-13 9:48 ` Elena Zannoni
2001-11-13 10:55 ` Tom Tromey
2001-11-26 19:26 ` Tom Tromey
2001-11-26 23:43 ` Eli Zaretskii
2001-11-14 11:56 ` Eli Zaretskii
2001-11-26 18:36 ` Elena Zannoni
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=8011-Thu04Oct2001090058+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.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