From: Baurzhan Ismagulov <ibr@radix50.net>
Subject: Re: bash and reverse-search-history
Date: Sat, 22 Apr 2006 14:24:59 +0200 [thread overview]
Message-ID: <20060422122458.GB4759@radix50.net> (raw)
In-Reply-To: <e2bkqa$lht$1@sea.gmane.org>
Hello Kevin,
On Fri, Apr 21, 2006 at 04:02:08PM -0600, Kevin Rodgers wrote:
> > 2. I couldn't find a way to search the whole bash history. When I type
> > some expression that I know is in ~/.bash_history, emacs says "Not
> > found".
>
> Does `C-h v comint-input-ring-file-name' in the *shell* buffer agree
> with "~/.bash_history"?
The command produces the following output:
comint-input-ring-file-name's value is "~/.bash_history"
Local in buffer *shell*; global value is nil
Documentation:
*If non-nil, name of the file to read/write input history.
See also `comint-read-input-ring' and `comint-write-input-ring'.
This variable is buffer-local, and is a good thing to set in mode hooks.
You can customize this variable.
Defined in `comint'.
I'm not sure what you mean by "agree". I'm able to scroll through
.bash_history via M-p, but M-r finds only expressions that I typed
during the current session.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2006-04-22 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 12:43 bash and reverse-search-history Baurzhan Ismagulov
2006-04-21 15:13 ` Peter Dyballa
2006-04-21 15:43 ` Baurzhan Ismagulov
2006-04-21 16:45 ` Drew Adams
2006-04-22 19:24 ` Baurzhan Ismagulov
2006-04-22 20:27 ` Drew Adams
2006-04-22 21:05 ` Baurzhan Ismagulov
2006-04-22 21:29 ` Peter Dyballa
2006-04-22 21:53 ` Baurzhan Ismagulov
2006-04-22 22:21 ` Peter Dyballa
2006-04-23 7:00 ` Baurzhan Ismagulov
2006-04-21 22:02 ` Kevin Rodgers
2006-04-22 12:24 ` Baurzhan Ismagulov [this message]
[not found] <mailman.700.1145623405.9609.help-gnu-emacs@gnu.org>
2006-04-22 9:18 ` Gary Wessle
2006-04-22 12:21 ` Baurzhan Ismagulov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060422122458.GB4759@radix50.net \
--to=ibr@radix50.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).