From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 58532@debbugs.gnu.org
Subject: bug#58532: 29.0.50; Support displaying imenu entries in a separate buffer
Date: Thu, 20 Oct 2022 00:03:09 +0200 [thread overview]
Message-ID: <m18rlbbheq.fsf@yahoo.es> (raw)
In-Reply-To: <86sfjkxk69.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 19 Oct 2022 23:50:14 +0300")
Juri Linkov <juri@linkov.net> writes:
>
> Unfortunately, mupdf/mutool doesn't support Unicode characters:
> https://bugs.ghostscript.com/show_bug.cgi?id=702358
> Maybe doc-view--pdf-outline could post-process the output
> to replace hex-encoded numbers with their character equivalents?
>
Do you mean for old versions of mupdf? IIUC, recent versions of mupdf
already do the right thing: They decode the runes (Unicode codepoints)
from the byte string and encode them in UTF-8, verbatim. Only control
characters are hex-encoded. I've opened in Emacs the PDF attached to
the mupdf bug report and it displays the outline correctly (mutool
version 1.19.0).
>
> 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.
next prev parent reply other threads:[~2022-10-19 22:03 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 [this message]
2022-10-20 7:43 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m18rlbbheq.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--cc=58532@debbugs.gnu.org \
--cc=juri@linkov.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.