From: Perry Smith <pedzan@icloud.com>
To: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: auto save for shell buffers
Date: Wed, 24 Jan 2018 13:13:26 -0600 [thread overview]
Message-ID: <6BE0267D-3411-48DC-A0AD-1C06D648EFED@icloud.com> (raw)
In-Reply-To: <mvminbrsjev.fsf@suse.de>
> 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
prev parent reply other threads:[~2018-01-24 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 19:01 auto save for shell buffers Perry Smith
2018-01-24 8:19 ` Robert Pluim
2018-01-24 9:19 ` Andreas Schwab
2018-01-24 19:13 ` Perry Smith [this message]
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=6BE0267D-3411-48DC-A0AD-1C06D648EFED@icloud.com \
--to=pedzan@icloud.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).