From: Drew Adams <drew.adams@oracle.com>
To: Tino Calancha <tino.calancha@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 24880@debbugs.gnu.org
Subject: bug#24880: 26.0.50; buff-menu: Command to unmark all buffers
Date: Sun, 6 Nov 2016 09:22:25 -0800 (PST) [thread overview]
Message-ID: <f2ea1e61-4f88-4dcf-b73c-a8d7f85f2336@default> (raw)
In-Reply-To: <87eg2ox0hi.fsf@gmail.com>
It would be far better, IMHO, to take the approach used by
Dired for this.
In Dired, `M-DEL' (or `* ?') unmarks a specific mark (e.g. D).
Or if it is followed directly by `RET', it unmarks all marks.
This is relevant and useful behavior for all contexts, such
as `*Buffer List*' (aka Buffer Menu), that let you mark
things in more than one way.
Users should be able to use `M-DEL' to selectively remove
any one of the marks (D, S, >,...) _or_ all marks together
(via `M-DEL RET').
The same approach should be taken for other, similar
buffers that list objects that can be marked in more than
one way, whether the objects be buffers (e.g. Ibuffer),
packages, files, bookmarks, or whatever else.
Besides giving users much more control, this provides a
consistent UI. Users will then use `M-DEL RET' as the
standard way to completely unmark an object.
This is the approach I took with Bookmark+, for instance.
It takes a tiny bit more work to implement, but the result
is far more useful for users.
(Just one opinion.)
next prev parent reply other threads:[~2016-11-06 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 10:04 bug#24880: 26.0.50; buff-menu: Command to unmark all buffers Tino Calancha
2016-11-05 10:17 ` Eli Zaretskii
2016-11-06 12:21 ` Tino Calancha
2016-11-06 17:22 ` Drew Adams [this message]
2016-11-14 10:29 ` Tino Calancha
2016-11-15 16:03 ` Eli Zaretskii
2016-11-16 10:09 ` Tino Calancha
2016-11-18 10:09 ` Eli Zaretskii
2016-11-18 10:17 ` Tino Calancha
2016-11-18 11:05 ` Eli Zaretskii
2016-11-07 18:38 ` Eli Zaretskii
2016-11-22 6:30 ` Tino Calancha
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=f2ea1e61-4f88-4dcf-b73c-a8d7f85f2336@default \
--to=drew.adams@oracle.com \
--cc=24880@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tino.calancha@gmail.com \
/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).