From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Kill all visited buffers
Date: Sat, 21 Nov 2015 21:44:06 +0100 [thread overview]
Message-ID: <87610vxeuh.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: mailman.404.1448137712.31583.help-gnu-emacs@gnu.org
Tim Johnson <tim@akwebsoft.com> writes:
> Google has failed me. I'm looking for a way to programmatically kill
> all _visited_ buffers.
>
> Any recommendations?
(require 'cl)
(mapc (function kill-buffer)
(remove-if-not (lambda (buffer)
(and (buffer-file-name buffer)
(file-exists-p (buffer-file-name buffer))))
(buffer-list)))
--
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
next parent reply other threads:[~2015-11-21 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.404.1448137712.31583.help-gnu-emacs@gnu.org>
2015-11-21 20:44 ` Pascal J. Bourguignon [this message]
2015-11-21 20:28 Kill all visited buffers Tim Johnson
2015-11-21 20:43 ` Drew Adams
2015-11-21 20:48 ` Tim Johnson
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=87610vxeuh.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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.
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).