From: Yuri Khan <yuri.v.khan@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "R. Diez" <rdiezmail-emacs@yahoo.de>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: kill-matching-buffers without confirmation
Date: Tue, 23 May 2017 12:28:35 +0700 [thread overview]
Message-ID: <CAP_d_8WuQY3UJj3ORhJT4TcK-vL4Mgc9yQp4HNDS8tmETjxiyg@mail.gmail.com> (raw)
In-Reply-To: <6e11051e-1a41-426b-97be-de1d70480c34@default>
On Tue, May 23, 2017 at 5:21 AM, Drew Adams <drew.adams@oracle.com> wrote:
> I don't even think that Emacs needs commands `kill-matching-buffers' and
> `kill-some-buffers' at all, for that matter.
>
> [What Emacs should offer instead is a way for `C-x k' to act (by hitting
> a key) on *each* completion of your input. And ways to match buffer names
> better, possibly choosing how on the fly: substring, regexp, fuzzy.
Another UI for the same use case is:
* Open up a buffer list (e.g. ibuffer).
* Mark buffers by regexp (‘% n’ in ibuffer).
* Inspect the list to ensure it’s what you expect. Possibly mark or unmark some.
* Kill marked buffers.
If any of those are unsaved, a prompt could offer the “yes for all”
choice, like ! does in query-replace.
next prev parent reply other threads:[~2017-05-23 5:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <537757403.6158992.1495470490914.ref@mail.yahoo.com>
2017-05-22 16:28 ` kill-matching-buffers without confirmation R. Diez
2017-05-22 18:21 ` Kaushal Modi
2017-05-22 18:34 ` Clément Pit-Claudel
2017-05-22 18:42 ` Kaushal Modi
2017-05-22 18:45 ` Clément Pit-Claudel
2017-05-22 19:00 ` Kaushal Modi
2017-05-22 19:13 ` Clément Pit-Claudel
2017-05-22 19:20 ` Kaushal Modi
2017-05-22 19:34 ` Stefan Monnier
2017-05-22 22:21 ` Drew Adams
2017-05-23 5:28 ` Yuri Khan [this message]
2017-05-23 6:28 ` R. Diez
2017-05-23 20:34 ` Drew Adams
2017-05-23 12:51 ` Kaushal Modi
2017-05-23 13:03 ` Stefan Monnier
2017-05-23 13:18 ` Kaushal Modi
2017-05-24 1:50 ` zhanghj
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=CAP_d_8WuQY3UJj3ORhJT4TcK-vL4Mgc9yQp4HNDS8tmETjxiyg@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rdiezmail-emacs@yahoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).