unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 18268@debbugs.gnu.org
Subject: bug#18268:
Date: Tue, 23 Feb 2016 23:21:43 +1100	[thread overview]
Message-ID: <87fuwjobvs.fsf@gnus.org> (raw)
In-Reply-To: <CAELgYhfGmQyk4+7DeJq5WXwXer-o9Dubie3oKP0AVouSnvVTCA@mail.gmail.com> (Carlos Pita's message of "Fri, 15 Aug 2014 12:18:36 -0300")

Carlos Pita <carlosjosepita@gmail.com> writes:

> The following is a simpler and more correct patch that also lets the
> user (final user or major mode developer) control whether the submenus
> are sorted or kept on top. The guiding idea is that there is two major
> ways to offer an imenu, according to the mode:
>
> 1) Some modes show a hierarchy of language objects. For example:
> python-mode will show class/method, function/nested function, etc.
> relationships; org-mode will show section/subsection/subsubsection/...
> hierarchies. In these cases keeping the submenus on top is not
> adequate since it creates an artificial split of the list.
>
> 2) Some modes show top level submenus with fixed categories
> (Functions, Classes, Variables, etc). These modes will presumably want
> to keep the submenus on top and sorted in the order they were given.
>
> 3) Other modes would not fit either (1) or (2). Then, there is always
> the possibility of turning off sorting and provide the menu structure
> as is.
>
> Regards
> --
> Carlos
>
> 156a157,161
>> (defcustom imenu-sort-submenus nil
>>   "Non-nil means Imenu should sort submenus also (using imenu-sort-function)."
>>   :type 'boolean
>>   :group 'imenu)

Could you resubmit this as a context patch instead of a "raw" patch?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2016-02-23 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 23:18 bug#18268: 24.3.92; Make imenu sort submenus also (fix included) carlosjosepita
2014-08-14 23:56 ` bug#18268: Carlos Pita
2014-08-15 15:18   ` bug#18268: Carlos Pita
2016-02-23 12:21     ` Lars Ingebrigtsen [this message]
2019-06-25 21:45       ` bug#18268: Lars Ingebrigtsen

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=87fuwjobvs.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18268@debbugs.gnu.org \
    --cc=carlosjosepita@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).