From: Hui Liu <liuhui.zy@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 8725@debbugs.gnu.org
Subject: bug#8725: imenu--split-menu should not deliver surprises
Date: Sun, 13 Apr 2014 11:44:36 +0800 [thread overview]
Message-ID: <CAB=Rzgn1FD40ZSrLWm1zTXt=jcPoed-qLYCB4k1K4=NrMourNw@mail.gmail.com> (raw)
In-Reply-To: <jwvbnw68gz1.fsf-monnier+emacsbugs@gnu.org>
I don't think it is better because it meaninglessly increases the
depth of menus. In fact, this problem mainly occurs in writing related
modes, and it is caused by the unreasonable sort in imenu--split-menu
instead of menus provided by these modes.
Is there any reason to put items with the submenu on top
indiscriminately? At least Imenu could provide an option about whether
to do so without regard to the original order of items. Then let the
major mode decide.
2014-04-13 4:03 GMT+08:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> and the reason is Imenu put items with submenus at the top. Such
>> behaviour may be reasonable for programming modes, but is clearly
>> unnecessary for text modes.
>
> Actually it doesn't have much to do with text-modes vs programming-modes
> but with the way the menu is built. E.g. the menu could look like
>
> Index
> |- ...
> Section 1
> Section 2
> Section 3
>
> if org-mode provided an "Index" submenu, in which case it would make a lot
> of sense to put it on top. So a better option is to let the major
> mode decide.
>
>
> Stefan
next prev parent reply other threads:[~2014-04-13 3:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 13:16 bug#8725: 23.2; imenu--split-menu should not deliver surprises dino chiesa
2014-04-12 13:52 ` bug#8725: " Hui Liu
2014-04-12 20:03 ` Stefan Monnier
2014-04-13 3:44 ` Hui Liu [this message]
2014-04-14 2:03 ` Stefan Monnier
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='CAB=Rzgn1FD40ZSrLWm1zTXt=jcPoed-qLYCB4k1K4=NrMourNw@mail.gmail.com' \
--to=liuhui.zy@gmail.com \
--cc=8725@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).