From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 1150@debbugs.gnu.org
Subject: bug#1150: 23.0.60; Ibuffer's menubar menu should be named Ibuffer, not View
Date: Wed, 27 Apr 2016 19:06:48 +0200 [thread overview]
Message-ID: <87h9engevr.fsf@gnus.org> (raw)
In-Reply-To: <87lh3zgf62.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 27 Apr 2016 19:00:37 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> "Drew Adams" <drew.adams@oracle.com> writes:
>
>> However, the `View' menu is still inappropriately named - it includes things
>> that have nothing to do with viewing (`Diff with file', `Toggle Auto Mode',
>> `Customize Ibuffer', `Filter', `Filter Groups'). It seems to be a catch-all - an
>> `Ibuffer' menu for things that don't fit in `Operate' or `Mark'. And menu
>> `Operate' includes some viewing menu items.
>>
>> I don't have a better name in mind than `View'. Instead, I'd suggest perhaps
>> reorganizing the menus. The organization of the Dired menus is superior and
>> might serve as a partial model.
>
> Yes, the organisation doesn't seem ideal. I think the "diff" should go
> to "Operate", at least. I don't mind the filter things in the "View"
> menu -- they do alter what you're viewing...
>
> Customize/toggle don't seem to belong in any of the existing menus.
Actually, the "toggle auto mode" does kinda belong in the "View" menu,
as long as we consider that menu to be both about viewing the buffers,
and organising the ibuffer buffer itself.
So I'd suggest just moving the "diff" to "Operate" and removing the
customisation menu item. I think that's a pretty unusual item to have
in the menu?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-27 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 16:54 bug#1150: 23.0.60; Ibuffer's menubar menu should be named Ibuffer, not View Drew Adams
2008-10-12 17:12 ` Drew Adams
2016-04-27 17:00 ` Lars Ingebrigtsen
2016-04-27 17:06 ` Lars Ingebrigtsen [this message]
2016-04-27 17:21 ` Drew Adams
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=87h9engevr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=1150@debbugs.gnu.org \
--cc=drew.adams@oracle.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).