all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Layer <layer@known.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Emacs-devel@gnu.org
Subject: Re: comint shell buffers autosaved to a file?
Date: Tue, 27 Mar 2018 16:39:32 -0700	[thread overview]
Message-ID: <CAGSZTj+UaLsRVCCFwzGviLYSL5+w7Cw_8TP=T5HKRB4Qbc44pg@mail.gmail.com> (raw)
In-Reply-To: <CAGSZTjKCR58rEnTM5=1PWmYqTXT5JmkQ6o11vDjzcBfUkXG_ew@mail.gmail.com>

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

I see this buffer local variable:

   (buffer-auto-save-file-name .
"/net/freon/home/layer/src/emacs/#%2Ashell%2A#8376MSi#")

but I generated a lot of output in the buffer and that file doesn't exist.

I'm thinking of using comint-output-filter-functions to implement this
directly, so the command output is saved when it is received by emacs.

On Tue, Mar 27, 2018 at 4:36 PM, Kevin Layer <layer@known.net> wrote:

> There's no file associated with a shell buffer, so where does it auto-save
> to?
>
> On Tue, Mar 27, 2018 at 4:13 PM, Andreas Schwab <schwab@linux-m68k.org>
> wrote:
>
>> On Mär 27 2018, Kevin Layer <layer@known.net> wrote:
>>
>> > Any ideas on this?  I'm willing to do some work to add it, if it's not
>> too
>> > hard.
>>
>> Just enable auto-save-mode.
>>
>> Andreas.
>>
>> --
>> Andreas Schwab, schwab@linux-m68k.org
>> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
>> "And now for something completely different."
>>
>
>

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

  reply	other threads:[~2018-03-27 23:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 22:00 comint shell buffers autosaved to a file? Kevin Layer
2018-03-27 23:13 ` Andreas Schwab
2018-03-27 23:36   ` Kevin Layer
2018-03-27 23:39     ` Kevin Layer [this message]
2018-03-27 23:42   ` Kevin Layer
2018-03-28 18:05     ` Kevin Layer
2018-03-29 20:34       ` Kalman Reti
2018-04-02 20:10         ` Juri Linkov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGSZTj+UaLsRVCCFwzGviLYSL5+w7Cw_8TP=T5HKRB4Qbc44pg@mail.gmail.com' \
    --to=layer@known.net \
    --cc=Emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.