From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: 10229@debbugs.gnu.org
Subject: bug#10229: save-some-buffers, -action-alist
Date: Tue, 06 Dec 2011 21:16:00 -0700 [thread overview]
Message-ID: <jbmp9f$h2q$1@dough.gmane.org> (raw)
In-Reply-To: <878vmqccd7.fsf@jidanni.org>
On 12/6/11 1:50 AM, jidanni@jidanni.org wrote:
> C-x s runs the command save-some-buffers, which is an interactive
> compiled Lisp function in `files.el'.
>
> It is bound to C-x s.
>
> (save-some-buffers&optional ARG PRED)
>
> Save some modified file-visiting buffers. Asks user about each one.
> You can answer `y' to save, `n' not to save, `C-r' to look at the
> buffer in question with `view-buffer' before deciding or `d' to
> view the differences using `diff-buffer-with-file'.
>
> OK, but you forgot one: plain old visit-the-buffer.
>
> C-r lets you look at it but you are still in the minibuffer.
That should not be. The buffer should be selected.
> So you hit C-g and ... you can't see it any more.
`q' is the usual way to exit View mode.
> This command first saves any buffers where `buffer-save-without-query' is
> non-nil, without asking.
>
> Optional argument (the prefix) non-nil means save all with no questions.
> Optional second argument PRED determines which buffers are considered:
> If PRED is nil, all the file-visiting buffers are considered.
> If PRED is t, then certain non-file buffers will also be considered.
> If PRED is a zero-argument function, it indicates for each buffer whether
> to consider it or not when called with that buffer current.
>
> See `save-some-buffers-action-alist' if you want to
> change the additional actions you can take on files.
>
> Well C-h v save-some-buffers-action-alist shows some horrid byte code.
Click on the link to files.el, which reveals the source code.
--
Kevin Rodgers
Denver, Colorado, USA
prev parent reply other threads:[~2011-12-07 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:50 bug#10229: save-some-buffers, -action-alist jidanni
2011-12-07 4:16 ` Kevin Rodgers [this message]
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='jbmp9f$h2q$1@dough.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--cc=10229@debbugs.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.