From: Peter Dyballa <Peter_Dyballa@web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Saving/Recalling Shell Commands History?
Date: Wed, 23 Aug 2006 17:20:37 +0200 [thread overview]
Message-ID: <023EA9DE-0B56-48B3-94E5-A82DE0EC69DB@web.DE> (raw)
In-Reply-To: <echo8a$vnh$1@sea.gmane.org>
Am 23.08.2006 um 16:20 schrieb Kevin Rodgers:
> I don't understand why it needs to be so complicated. What do you
> mean by "separate the different Emacs versions [you] are using"? None
> of your code references emacs-version, emacs-major-version, or
> emacs-minor-version.
>
>> Here is my extended hook:
>> (add-hook 'shell-mode-hook
>> (lambda ()
>> (setq comint-input-ring-file-name
>> (expand-file-name "history" desktop-dirname))
>> (setq histfile_cmd (format
>> "echo \"set histfile = %s\" > .emacs_tcsh-init"
>> comint-input-ring-file-name))
>> (shell-command histfile_cmd)
>> ))
Desktop-dirname points to the different emacs-major-versions. My
purpose is to have the history files unchanged while I launch a
Carbon Emacs or an Emacs.app, which otherwise would write /their/
history into the same file. And when I'll start to have an intel
based Mac with Vanderpool built-in I also could run some Losedows,
Linux, Solaris, or other BSD Emacsen ...
What I wonder is whether GNU Emacs caches the contents of the history
file. If the contents of the history file changes by interaction of
some other shell, /my/ Emacs shell would find the other's history if
it would re-read the history file.
(BTW, it worked in Emacs shell with the default ~/.tcsh_history file,
although comint-input-ring-file-name pointed to some completely
different file. Could be shell-mode could not find a command from the
history file, but then tcsh would succeed.)
--
Greetings
Pete
Well done is better than well said.
-- Benjamin Franklin
next prev parent reply other threads:[~2006-08-23 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 15:07 Saving/Recalling Shell Commands History? gamename
2006-08-21 16:35 ` Drew Adams
2006-08-21 20:09 ` Peter Dyballa
2006-08-21 20:17 ` Drew Adams
2006-08-21 21:08 ` Peter Dyballa
2006-08-21 21:30 ` Drew Adams
2006-08-21 21:32 ` Kevin Rodgers
2006-08-21 22:14 ` Peter Dyballa
2006-08-22 23:13 ` Peter Dyballa
2006-08-23 14:20 ` Kevin Rodgers
2006-08-23 15:20 ` Peter Dyballa [this message]
2006-08-21 20:19 ` Jesse Alama
2006-08-21 21:11 ` Peter Dyballa
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=023EA9DE-0B56-48B3-94E5-A82DE0EC69DB@web.DE \
--to=peter_dyballa@web.de \
--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).