From: Peter Dyballa <Peter_Dyballa@web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Saving/Recalling Shell Commands History?
Date: Mon, 21 Aug 2006 22:09:02 +0200 [thread overview]
Message-ID: <D6613081-5D3D-44F6-9401-A4F27B44598A@web.DE> (raw)
In-Reply-To: <1156172846.553787.214050@h48g2000cwc.googlegroups.com>
Am 21.08.2006 um 17:07 schrieb gamename:
> Hi,
>
> Is there any way to save the commands issued in shell-mode and recall
> them when a new shell starts, or even in a new instance of emacs?
>
The documentation writes:
(defun comint-read-input-ring (&optional silent)
"Set the buffer's `comint-input-ring' from a history file.
The name of the file is given by the variable `comint-input-ring-
file-name'.
The history ring is of size `comint-input-ring-size', regardless of
file size.
If `comint-input-ring-file-name' is nil this function does nothing.
(defun comint-write-input-ring ()
"Writes the buffer's `comint-input-ring' to a history file.
The name of the file is given by the variable `comint-input-ring-
file-name'.
The original contents of the file are lost if `comint-input-ring' is
not empty.
If `comint-input-ring-file-name' is nil this function does nothing.
Although I have set comint-input-ring-file-name, this file never gets
written. And neither read (I've put some uniq commands into it to see
if). All *shell* does in my case, is it reads ~/.tcsh_history –
because I have tcsh as login shell.
Could be there is bug, or I simply need to activate the described
behaviour with some start-up or shut-down hooks ...
--
Greetings
Pete
»¿ʇı̣ əsnqɐ ʇ,uɐɔ noʎ ɟı̣
ɓuı̣ɥʇʎuɐ sı̣ pooɓ ʇɐɥʍ«
next prev parent reply other threads:[~2006-08-21 20:09 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 [this message]
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
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=D6613081-5D3D-44F6-9401-A4F27B44598A@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).