Re: go to next unsaved buffer

[Dan Jacobson]

>>>>> "P" == Paul Stoeber <paul.stoeber@stud.tu-ilmenau.de> writes:

P> On Wed, Jul 03, 2002 at 01:30:16PM +0800, Dan Jacobson wrote:
Paul> `save-some-buffers' already has this: C-r.  Type C-M-c to exit from
Paul> the recursive edit.
>> 
>> It is a bug that C-h k C-x s does not mention this.

P> The prompt "Save file /tmp/1? (y, n, !, ., q, C-r or C-h)"
P> mentions C-r, and C-h explains it.

not good enough.  I want to know what I am in for before I press the
key, that's only fair and square.  What if all the C-s features were
only learnable once one was already searching.  [p.s. not talking
about reading Info here, just C-h k]

>> By the way I just tired what you mentioned.  Seems like a great way to
>> get all confused.  I ended up with lots of [[[ ]]] in the modeline and
>> I had to hit exit-recursive-edit several times to get out.

>> idea is simpler in that you aren't under the gun of being in the
>> middle of answering the question of saving each buffer.

P> I've tried your idea, and it's actually more comfortable than the
P> the dialog with `save-some-buffers'.

P> A problem is: what is an "unsaved buffer"?

i mean the kind that C-x s would ask about, with files attached.
Oh, and then there's some gnus draft buffers too...

P> (defun switch-to-next-unsaved-buffer ()

a quick test of your function seems that it does it all... hope to see
it in emacs soon, along with an official keybinding.  Pretty darn
handy actually.

uh oh, want to exclude modified *scratch* type buffers... and some
users would want *shell* to be included which seems not to now...
ok, this all should have customization instructions...
better yet, a handy 'only-if-file-associated 'processes[-too]
.... etc. predicates list...
-- 
http://jidanni.org/ Taiwan(04)25854780