From: Bob Rossi <bob@brasko.net>
To: Greg Law <greg@greglaw.net>
Cc: gdb@sources.redhat.com, Julian Smith <jules@op59.net>
Subject: Re: Using C-s to forward search command history
Date: Fri, 19 Aug 2005 13:31:00 -0000 [thread overview]
Message-ID: <20050819133055.GB18911@white> (raw)
In-Reply-To: <4305DACB.7010604@greglaw.net>
> If I've read the info pages correctly, I can use C-s in order to search
> the command history forwards. However, this sequence also seems to be
> the control sequence to suspend the terminal :-(
>
> Have I misunderstood, or is there a way round this? (It would be very
> useful for me to be able to search forwards).
This is not a GDB issue, it's a readline issue. Try doing the same thing
with while using the bash shell. You might be able to remap the
functionality of forward-search-history in your .inputrc.
Bob Rossi
next prev parent reply other threads:[~2005-08-19 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 13:12 Greg Law
2005-08-19 13:31 ` Bob Rossi [this message]
2005-08-20 12:18 ` Michael Veksler
2005-08-20 13:20 ` Bob Rossi
2005-08-20 16:05 ` Michael Veksler
2005-08-20 17:23 ` Andreas Schwab
2005-08-20 17:55 ` Dan Kegel
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=20050819133055.GB18911@white \
--to=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=greg@greglaw.net \
--cc=jules@op59.net \
/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).