From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: changing comint-input-ring-file-name in process in shell
Date: Sat, 07 Nov 2009 00:10:28 -0700 [thread overview]
Message-ID: <hd36gu$u57$1@ger.gmane.org> (raw)
In-Reply-To: <87my2z88g2.fsf@kolob.sebmags.homelinux.org>
Seb wrote:
> Hi,
>
> A program that runs in shell mode uses a local history file. Therefore,
> I'd like to set `comint-input-ring-file-name' to that file. I use the
> program by doing "M-x shell", and then start the program in the shell
> buffer by typing its name and hitting ENTER. The program's prompt
> replaces the shell's at this point. I thought that subsequently
> evaluating the following in the shell buffer would allow me to cycle
> through the local history file:
>
> (setq comint-input-ring-file-name
> "/path/to/local/.bash_history"))
>
> However, cycling with "M-p" or "M-n" cycles the input through the
> initial `comint-input-ring-file-name' set by the shell buffer, in my
> case ~/.bash_history since I'm using bash. Doing "C-h v
> comint-input-ring-file-name" does show the new value
> ("/path/to/loca/.bash_history"), so I don't understand what is going
> on. Any help would be appreciated.
The file is read once by shell-mode (not comint-mode), when you execute
`M-x shell'. That is why the doc string for comint-input-ring-file-name
says "This variable is buffer-local, and is a good thing to set in mode hooks."
How about:
(let ((comint-input-ring-file-name "/path/to/local/.bash_history"))
(shell))
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2009-11-07 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 0:50 changing comint-input-ring-file-name in process in shell Seb
2009-11-07 7:10 ` Kevin Rodgers [this message]
2009-11-07 21:44 ` Seb
2009-11-08 17:57 ` Seb
2009-11-11 14:47 ` Kevin Rodgers
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='hd36gu$u57$1@ger.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).