GNU bug report logs -
#381
save-some-buffers recursive editing entrapment
Previous Next
Reported by: jidanni <at> jidanni.org
Date: Mon, 9 Jun 2008 23:45:03 UTC
Severity: normal
Done: Stefan Monnier <monnier <at> iro.umontreal.ca>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Let's examine the trouble one can get into with
C-x s runs the command save-some-buffers
Type SPC or `y' to save the current buffer;
DEL or `n' to skip the current buffer;
RET or `q' to give up on the save (skip all remaining buffers);
C-g to quit (cancel the whole command);
! to save all remaining buffers;
C-r to view this buffer;
Yeah, that will get one entangled into both recursive editing and view
mode, try it while you are entering the reply for this message.
d to view changes in this buffer;
Beep: "Buffer *mail* has no associated file on disc" (so don't ask in
this case); plus now we are recursive editing.
or . (period) to save the current buffer and exit.
Make you a deal: please just add a further choice:
g go to the current buffer (i.e., that buffer listed)
with no side effects, no marriage vows. Just put us in that buffer and
that's that.
4 out of 5 users won't know how to climb out of recursive editing, now
that there is no message about it, except for brackets in the
modeline. And even if there was a message, it would get overwritten by
the view mode message. And, recursive editing messes up gnus for me.
So my new g proposal will not tangle up the user with recursive editing.
This bug report was last modified 16 years and 351 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.