From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: Patch: operate-and-get-next
Date: Fri, 28 Sep 2001 09:36:00 -0000 [thread overview]
Message-ID: <874rpntg7n.fsf@creche.redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0109280919240.16046-100000@makita.cygnus.com>
>>>>> "Keith" == Keith Seitz <keiths@cygnus.com> writes:
>> What you do is use C-p to find the first command in a sequence. You
>> use C-o to execute it (like pressing Enter), and when the next prompt
>> comes up, the next command from history is already inserted for you.
Keith> This is too cool. I never even knew this existed! :-)
Yeah. I've used it every day since I first found out about it.
Keith> I use the console quite a bit, too, but I do it 75% of the time
Keith> because it helps elide problems with gdb and insight getting
Keith> out of sync.(Try up/down in the console window. It doesn't work
Keith> properly.)
Yeah. I've noticed other things like this, but offhand I don't recall
what they are. I'll try to start submitting PRs when I find them. I
know the console is a low priority; that's fine. But we should still
keep track of these problems. I'll submit the up/down one.
Keith> Could you change this to the "new" comment format? I know, this
Keith> isn't documented anywhere... I started doing this in
Keith> regwin.it[hb] when I tweaked the register window.
No problem, especially given that you wrote it for me :-)
Keith> Otherwise, APPROVED! :-) (Wow, a new feature. Where's my
Keith> champagne?)
It's in.
Keith> Now all we need to do is get ^R working...
That would be a lot more work :-(
Tom
next prev parent reply other threads:[~2001-09-28 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 9:15 Tom Tromey
2001-09-28 9:27 ` Keith Seitz
2001-09-28 9:36 ` Tom Tromey [this message]
2001-09-28 9:40 ` Keith Seitz
2001-09-28 9:54 ` John R. Moore
2001-09-28 10:12 ` Tom Tromey
2001-09-28 10:19 ` Tom Tromey
2001-09-28 10:27 ` Keith Seitz
2001-09-28 10:41 ` Tom Tromey
2001-09-28 11:03 ` Keith Seitz
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=874rpntg7n.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=insight@sourceware.cygnus.com \
--cc=keiths@cygnus.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).