auto save for shell buffers

auto save for shell buffers

[Perry Smith]

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

How can I set things up so the buffer being used to run an inferior shell will be autosaved periodically to a file?

The file to save in could be named "shell-2018-01-22".

I thought this would be trivial but it seems the autosave concept is deeply tied into the visiting file concepts which of course, doesn't apply for the buffer being used by the inferior shell.

The reason is because twice this past month my emacs had died. Usually its not a big deal but in these last two cases, it was frustrating enough to prompt me into trying to figure out a solution.

Thank you in advance
Perry



[-- Attachment #2: Type: text/html, Size: 988 bytes --]

Re: auto save for shell buffers

[Robert Pluim]

Perry Smith <pedzan@icloud.com> writes:

> How can I set things up so the buffer being used to run an inferior shell will be autosaved periodically to a file?
>
> The file to save in could be named "shell-2018-01-22".
>
> I thought this would be trivial but it seems the autosave concept is
> deeply tied into the visiting file concepts which of course, doesn't
> apply for the buffer being used by the inferior shell.
>

I'm not sure why you think that. You can save the shell buffer to a
file, and it will be autosaved. Note that the shell buffer doesn't
have to be called "*shell*"

Robert

Re: auto save for shell buffers

[Andreas Schwab]

On Jan 24 2018, Robert Pluim <rpluim@gmail.com> wrote:

> Perry Smith <pedzan@icloud.com> writes:
>
>> How can I set things up so the buffer being used to run an inferior shell will be autosaved periodically to a file?
>>
>> The file to save in could be named "shell-2018-01-22".
>>
>> I thought this would be trivial but it seems the autosave concept is
>> deeply tied into the visiting file concepts which of course, doesn't
>> apply for the buffer being used by the inferior shell.
>>
>
> I'm not sure why you think that. You can save the shell buffer to a
> file, and it will be autosaved. Note that the shell buffer doesn't
> have to be called "*shell*"

Also, auto-save handles non-file buffers as well.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Re: auto save for shell buffers

[Perry Smith]

> On Jan 24, 2018, at 3:19 AM, Andreas Schwab <schwab@suse.de> wrote:
> 
> On Jan 24 2018, Robert Pluim <rpluim@gmail.com> wrote:
> 
>> Perry Smith <pedzan@icloud.com> writes:
>> 
>>> How can I set things up so the buffer being used to run an inferior shell will be autosaved periodically to a file?
>>> 
>>> The file to save in could be named "shell-2018-01-22".
>>> 
>>> I thought this would be trivial but it seems the autosave concept is
>>> deeply tied into the visiting file concepts which of course, doesn't
>>> apply for the buffer being used by the inferior shell.
>>> 
>> 
>> I'm not sure why you think that. You can save the shell buffer to a
>> file, and it will be autosaved. Note that the shell buffer doesn't
>> have to be called "*shell*"
> 
> Also, auto-save handles non-file buffers as well.

So, based upon Robert’s input, I did a write buffer to a file and it is now auto saving the buffer.

But Andreas’ reply had me even more curious.  So I started another shell and just did “auto-save-mode” which turned on auto-save mode (dahhh) and now there is a file called #%2Ashell%2A#38994078EmN# in that directory.

YIPPIE!!!

Perry