From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: operate-and-get-next
Date: Thu, 04 Oct 2001 18:16:00 -0000 [thread overview]
Message-ID: <87y9mqj2n5.fsf@creche.redhat.com> (raw)
In-Reply-To: <8011-Thu04Oct2001090058+0300-eliz@is.elta.co.il>
>>>>> "Eli" == Eli Zaretskii <eliz@is.elta.co.il> writes:
Eli> I was missing such a feature as well. Thanks for implementing it.
You're welcome.
>> The appended patch implements this new readline command and gives
>> it the same binding in gdb that it has in bash.
Eli> I think we should mention this in the "Command Syntax" section,
Eli> where the action of RET is described.
Thanks. How about the appended?
I took the bulk of the text from the Bash manual.
Tom
Index: doc/ChangeLog
from Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Command Syntax): Document C-o binding.
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.51
diff -u -r1.51 gdb.texinfo
--- doc/gdb.texinfo 2001/09/12 19:49:52 1.51
+++ doc/gdb.texinfo 2001/10/05 00:34:19
@@ -1190,6 +1190,13 @@
nothing. This is useful mainly in command files (@pxref{Command
Files,,Command files}).
+@cindex repeating command sequences
+@kindex C-o @r{(operate-and-get-next)}
+The @kbd{C-o} binding is useful for repeating a complex sequence of
+commands. This command accepts the current line, like @kbd{RET}, and
+then fetches the next line relative to the current line from the history
+for editing.
+
@node Completion
@section Command completion
next prev parent reply other threads:[~2001-10-04 18:16 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
2001-10-04 18:16 ` Tom Tromey [this message]
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=87y9mqj2n5.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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