unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: 58532@debbugs.gnu.org
Subject: bug#58532: 29.0.50; Support displaying imenu entries in a separate buffer
Date: Thu, 20 Oct 2022 10:43:44 +0300	[thread overview]
Message-ID: <86edv3djdz.fsf@mail.linkov.net> (raw)
In-Reply-To: <m18rlbbheq.fsf@yahoo.es> ("Daniel Martín"'s message of "Thu, 20 Oct 2022 00:03:09 +0200")

>> The problem is that imenu-submenus-on-top is t by default,
>> but such order is incompatible with the outline-mode trees.
>> For example, all functions belong to the Variables outline:
>>
>> * Types
>>   imenu
>>   imenu-unavailable
>> * Variables
>>   imenu-after-jump-hook
>>   imenu-auto-rescan
>>   imenu-auto-rescan-maxout
>>   ...
>> imenu
>> imenu--cleanup
>> imenu--completion-buffer
>> imenu--create-keymap
>> ...
>
> That's a good point.  Perhaps we need to create a special mode to
> display the imenu hierarchy.

This problem occurs only when MENU-TITLE is nil in imenu-generic-expression.
We could invent a fictitious outline heading for such empty titles, e.g.
"All" or "Other".  Then it will have own outline:

* Types
  imenu
  imenu-unavailable
* Variables
  imenu-after-jump-hook
  imenu-auto-rescan
  imenu-auto-rescan-maxout
  ...
* Other
  imenu
  imenu--cleanup
  imenu--completion-buffer
  imenu--create-keymap
  ...





  reply	other threads:[~2022-10-20  7:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1v8ol6h7y.fsf.ref@yahoo.es>
2022-10-15  0:52 ` bug#58532: 29.0.50; Support displaying imenu entries in a separate buffer Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 14:51   ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 23:58     ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 11:45       ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 13:10         ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 14:51   ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-19 20:50   ` Juri Linkov
2022-10-19 21:35     ` Jose A. Ortega Ruiz
2022-10-19 21:51       ` Stephen Berman
2022-10-20  7:38         ` Juri Linkov
2022-10-19 23:00       ` Jose A. Ortega Ruiz
2022-10-20  7:39         ` Juri Linkov
2022-10-19 22:03     ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-20  7:43       ` Juri Linkov [this message]
2024-05-10 16:42         ` Juri Linkov
2024-05-28 17:55           ` Juri Linkov

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=86edv3djdz.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=58532@debbugs.gnu.org \
    --cc=mardani29@yahoo.es \
    /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).