From: John Mastro <john.b.mastro@gmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Cc: Rolf Ade <rolf@pointsman.de>
Subject: Re: List of buffers under version control?
Date: Thu, 28 Jul 2016 14:14:50 -0700 [thread overview]
Message-ID: <CAOj2CQQOmf4ab-uqmXCPqt6qzMbeR7fhNEqjvKa-kry4f9w1yA@mail.gmail.com> (raw)
In-Reply-To: <87k2g5v5nk.fsf@linux-qg7d.fritz.box>
Rolf Ade <rolf@pointsman.de> wrote:
> Thank you. That was the missing bit.
>
> Something like this is it:
>
> (loop for buffer in (buffer-list)
> until (if (vc-backend (buffer-file-name buffer))
> (buffer-modified-p buffer))
> finally return (if (and (buffer-modified-p buffer)
> (vc-backend (buffer-file-name buffer)))
> 1
> 0))
>
Glad it helps. You could do something like this to avoid repeating the
calls to `vc-backend' and `buffer-modified-p':
(if (loop for buffer in (buffer-list)
thereis (and (vc-backend (buffer-file-name buffer))
(buffer-modified-p buffer)))
1
0)
> Yes. This doesn't apply in my case, because I'm 'quering' emacs from
> within a script with the help of emacsclient -e and want just a yes / no
> answer (hence the 'un-lispish' return values). I just want to know, if
> this is the case (and ask for confirmation, to give me a chance to look
> at the thing, instead of just saving).
Not sure if it makes a difference for your use case, but
`save-some-buffers' does ask for confirmation before saving each buffer.
John
next prev parent reply other threads:[~2016-07-28 21:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 0:03 List of buffers under version control? Rolf Ade
2016-07-28 4:05 ` Rusi
2016-07-28 19:31 ` Rolf Ade
2016-07-28 19:52 ` John Mastro
2016-07-28 19:58 ` John Mastro
2016-07-28 19:56 ` Marcin Borkowski
[not found] ` <mailman.2241.1469735551.26859.help-gnu-emacs@gnu.org>
2016-07-28 21:01 ` Rolf Ade
2016-07-28 21:14 ` John Mastro [this message]
2016-07-28 21:25 ` Drew Adams
[not found] ` <mailman.2253.1469741176.26859.help-gnu-emacs@gnu.org>
2016-07-28 22:27 ` Rolf Ade
[not found] ` <mailman.2252.1469740513.26859.help-gnu-emacs@gnu.org>
2016-07-28 21:52 ` Rolf Ade
2016-07-29 1:42 ` Stefan Monnier
2016-07-28 5:12 ` Yuri Khan
[not found] ` <mailman.2177.1469682795.26859.help-gnu-emacs@gnu.org>
2016-07-28 19:31 ` Rolf Ade
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOj2CQQOmf4ab-uqmXCPqt6qzMbeR7fhNEqjvKa-kry4f9w1yA@mail.gmail.com \
--to=john.b.mastro@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rolf@pointsman.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).