|
|
|
|
| Re: Command line history in IDLWAVE shell [message #46087 is a reply to message #46086] |
Wed, 02 November 2005 17:53   |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Wed, 02 Nov 2005 16:11:26 -0800, Ed Hyer wrote:
> Currently set to a paltry 32 lines. Can't find a setting in the IDLWAVE
> manual to change this, sure of course that one exists. Using an older
> version of IDLWAVE right now, when I see the Unix guys they haven't had
> their coffee yet, and I'm not going to ask them until they do, if you know
> what I mean. But if the buffer exists, I'm sure the setting exists, too, I
> just can't find it.
This is actually a setting of comint. I use:
(setq comint-input-ring-size 1024)
in my .emacs.
JD
|
|
|
|
| Re: Command line history in IDLWAVE shell [message #88604 is a reply to message #46087] |
Fri, 16 May 2014 11:39 |
MarioIncandenza
Messages: 231
Registered: February 2005
|
Senior Member |
|
|
On Wednesday, November 2, 2005 6:53:32 PM UTC-7, JD Smith wrote:
> This is actually a setting of comint. I use:
> (setq comint-input-ring-size 1024)
> in my .emacs.
> JD
Next Q: The behavior I am used to is that the command-line history persists within an emacs session. I can 'exit' IDL and come back to it, but as long as it's within the same emacs session, I keep my history. But working on a new machine, I discovered that IDLWAVE is now saving the history into ~/.idlwave/idlwhist, and it is persistent across emacs sessions. I don't think I want this, because 1) the most important thing I do with the history is redo my initialization, which means "initialization for this day's work on this project," not "whatever I happened to be doing 1000 lines ago." Also, 2) I don't know what would happen if I was running two IDLWAVE sessions (happens all the time).
How can I get back to the old behavior where the history was only retained within a single emacs session?
--Edward H.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
