[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: I want an unsaveable buffer

From: Doug Lewan
Subject: RE: I want an unsaveable buffer
Date: Tue, 5 Aug 2014 13:22:14 +0000

Thanks for the suggestion. I'm not fluent in advice, but it has on occasion 
been very useful. I'll study this.

Douglas Lewan
Shubert Ticketing
(201) 489-8600 ext 224

Hazmat condition: There's some emacs on the floor.

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of Kevin Rodgers
> Sent: Tuesday, 2014 August 05 01:28
> To: address@hidden
> Subject: Re: I want an unsaveable buffer
> On 8/4/14 9:48 AM, Doug Lewan wrote:
> > I work in *scratch* a lot, /and/ I save (C-xC-s) very frequently just
> as a matter of habit. The consequence is that I find myself typing to
> the "File to save in:" prompt when I just want to continue working.
> >
> > Turning off or remapping C-xC-s in *scratch* is easy enough, but the
> obviously useful generalization is to turn saving off in any new buffer
> not associated with a regular file. (Writing buffer contents would
> remain, but you already have to think when you want that.)
> >
> > The natural route is to write a hook for buffer creation. The only
> hook I can find for that is buffer-list-update-hook which is also run
> on renaming, deletion, etc. I can imagine grabbing the output of
> (backtrace) to look at how the hook was called, but that no longer
> feels natural to me.
> >
> > Does anyone know of a natural approach to this?
> (defadvice save-buffer (around interactive-no-visited-file-name
> activate)
>    "When called interactively, disable for buffers not visiting a
> file."
>    (when (or (not (called-interactively-p 'any))
>            buffer-file-name)
>      ad-do-it))
> --
> Kevin Rodgers
> Denver, Colorado, USA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]