Re: I want an unsaveable buffer

[Grant Rettke]

Totally understood and now I want to tell you on real-auto-save
because I too am a recovering C-x C-s addict.

I add a hook to any buffer that needs it and forget about worrying
about saving all the time.
Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson


On Mon, Aug 4, 2014 at 10:48 AM, Doug Lewan <dougl@shubertticketing.com> 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?
>
> Thanks.
>
> ,Doug
> Douglas Lewan
> Shubert Ticketing
> (201) 489-8600 ext 224
>
> Hazmat condition: There's some emacs on the floor.
>
>
>