From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Felician Nemeth <felician.nemeth@gmail.com>,
58892@debbugs.gnu.org
Subject: bug#58892: 29.0.50; [PATCH] eglot-manual: Open the local info documentation
Date: Sun, 30 Oct 2022 08:42:32 -0400 [thread overview]
Message-ID: <jwvpme95vwd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83r0ypfwcq.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 30 Oct 2022 12:18:29 +0200")
>> Eglot now has a beautiful documentation in info format. This patch
>> let the user open it from Eglot's menu.
>>
>> BTW, the menu is the mode-line and I think it cannot be accessed using
>> only the keyboard. Would it make sense to put this menu in the "Tools"
>> part of the menu-bar as well?
>
> I'm unsure about any of this. We don't do anything like that for any
> other mode, AFAIR. And Eglot's main features are already mentioned in
> short in the Emacs user manual.
>
> What do others think? Lars, Stefan?
I don't think it makes much sense to add this specifically for
Eglot, indeed. It might make sense OTOH to add to the Help menu an
entry that lets you jump directly to the docs relevant to the current
modes.
It could be a submenu generated by considering the list of all currently
active minor modes (buffer-local and global) plus the current major mode
(and its parents, maybe?) and for each one of them try and find out
where they might be documented (e.g. relying on a symbol property
to map a mode to its Info node?).
Stefan
next prev parent reply other threads:[~2022-10-30 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 9:05 bug#58892: 29.0.50; [PATCH] eglot-manual: Open the local info documentation Felician Nemeth
2022-10-30 10:18 ` Eli Zaretskii
2022-10-30 12:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-30 12:53 ` Eli Zaretskii
2022-10-30 13:32 ` Felician Nemeth
2022-10-30 14:02 ` Eli Zaretskii
2022-10-31 13:22 ` João Távora
2022-10-31 13:36 ` Eli Zaretskii
2022-11-11 13:05 ` Stefan Kangas
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=jwvpme95vwd.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=58892@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=larsi@gnus.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).