From: Dan Jacobson <jidanni@dman.ddts.net>
Cc: bug-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: go to next unsaved buffer
Date: 04 Jul 2002 14:59:29 +0800 [thread overview]
Message-ID: <ag1bpv$42a$2@main.gmane.org> (raw)
In-Reply-To: <20020703121653.GA179@xyz>
>>>>> "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
next prev parent reply other threads:[~2002-07-04 6:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 8:11 go to next unsaved buffer Dan Jacobson
2002-07-02 10:38 ` Paul Stoeber
2002-07-03 5:30 ` Dan Jacobson
2002-07-03 12:16 ` Paul Stoeber
2002-07-03 12:16 ` Paul Stoeber
2002-07-03 18:57 ` Andreas Schwab
2002-07-03 18:57 ` Andreas Schwab
2002-07-04 6:59 ` Dan Jacobson [this message]
2002-07-04 6:59 ` Dan Jacobson
2002-07-04 18:24 ` Richard Stallman
2002-07-04 20:02 ` Paul Stoeber
2002-07-04 21:46 ` more official key bindings for us follow the leader types Dan Jacobson
2002-07-05 8:54 ` Miles Bader
2002-07-05 22:05 ` go to next unsaved buffer Richard Stallman
2002-07-06 7:37 ` bind me a/k/a leadership in the key binding dept Dan Jacobson
2002-07-06 10:42 ` Miles Bader
2002-07-03 20:57 ` go to next unsaved buffer Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ag1bpv$42a$2@main.gmane.org' \
--to=jidanni@dman.ddts.net \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.