From: Ed Peschko <esp5@mdssdev05.comp.pge.com>
To: gdb@sources.redhat.com
Subject: Re: intelligent history and memory for gdb
Date: Wed, 20 Jul 2005 21:24:00 -0000 [thread overview]
Message-ID: <20050720212440.GA20444@mdssdev05.comp.pge.com> (raw)
In-Reply-To: <1121795467.3476.ezmlm@sources.redhat.com>
> On Monday 18 July 2005 02:29 pm, Ed Peschko wrote:
> > in my .tcshrc, and was wondering if gdb has an equivalent. This allows me
> > to type:
> >
> > mak
> >
> > then up arrow, to see all the list of commands that I've typed in my
> > history that start with 'mak', instead of just forgetting that I've typed
> > 'mak' and going back to the last typed command (like gdb does by default).
>
> ctrl-r works for me from the (gdb) prompt to do a reverse-i-search.
Just curious, but how do you map this to up arrow? What's the equivalent for
forward-i-search?
As for the recording and importing history features, I'm assuming that they don't
exist? Is there a roadmap for 7.0?
Ed
next parent reply other threads:[~2005-07-20 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1121795467.3476.ezmlm@sources.redhat.com>
2005-07-20 21:24 ` Ed Peschko [this message]
2005-07-20 21:57 ` Jon Ringle
2005-07-18 18:30 Ed Peschko
2005-07-18 18:48 ` Jon Ringle
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=20050720212440.GA20444@mdssdev05.comp.pge.com \
--to=esp5@mdssdev05.comp.pge.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).