Re: Keep losing work in non-file-visiting buffers

[sebyte <sdt133@netscape.net>]

 > Since *info* and *Help* buffers are never(?) marked as modified, I guess
 > it's actually save-buffers-kill-emacs (C-x C-c) that's holding you up, not
 > kill-buffer (C-x k).  And that means it's buffer-offer-save that's at fault,
 > not kill-buffer-query-functions.
 >
 > So maybe you just want to turn on buffer-offer-save for buffers you explictly 
 > create, as with switch-to-buffer (C-x b), instead of buffers Emacs creates 
for > you:
 >
 > (defadvice switch-to-buffer (after buffer-offer-save activate)
 >   "Set `buffer-offer-save' when called interactively."
 >   (and (interactive-p)
 >        (setq buffer-offer-save t))) ; automatically local in all buffers

once again i've spoken too soon. things are much better but still not perfect. 
there are buffers in use that don't appear in *Buffer List* such as *temp* which 
i have to kill each time I use 'C-x d' to view a directory.  also Python mode 
uses temporary buffers which I now have to 'confirm kill'.

this is proving to be a lot more involved than i thought.  i just wish i knew 
even a tiny little amount of elisp and could do some problem solving on this one 
myself.  i will learn, eventually...

sebyte