From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, Felician Nemeth <felician.nemeth@gmail.com>,
monnier@iro.umontreal.ca, 58892@debbugs.gnu.org
Subject: bug#58892: 29.0.50; [PATCH] eglot-manual: Open the local info documentation
Date: Mon, 31 Oct 2022 13:22:56 +0000 [thread overview]
Message-ID: <CALDnm52vmVRgcqX0Qv3MUU60KyoTz2hGDa=u-TB+v-xXjxkmPw@mail.gmail.com> (raw)
In-Reply-To: <83bkptflzu.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
On Sun, Oct 30, 2022 at 2:02 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Currently, Eglot has a menu item that opens
> > https://github.com/joaotavora/eglot#readme. I think opening that URL
> > doesn't make sense anymore since eglot.texi is the primary source of the
> > documentation. Is it OK then to remove this menu item?
>
> Fine by me, but please wait for João to chime in.
>
Yes, it's fine. Show a patch and or push directly if you have permissions.
> > (The last item in message-mode-menu is "Message manual", so there is
> > prior art to what the patch of this bug report tries to achieve.)
>
> I think that's an exception rather than a rule. Mode-specific menus
> rarely have an item for their manuals. And Eglot should need that
> less than others, since most of its features just provide backends for
> existing Emacs features.
>
Yes, that's true. But users are not really familiar with all of them: they
don't
have the visibility that Eglot has. So Felicián's idea makes sense to me,
judging from these years of watching the Eglot bug tracker (where Felicián
is a long-time regular, which would explain why he thinks this feature is
useful).
If there was a keybinding C-xyz so that C-xyz RET eglot RET would land
one in the Eglot manual within Emacs, I think that would come some
way. Maybe there is this binding?
João
[-- Attachment #2: Type: text/html, Size: 2164 bytes --]
next prev parent reply other threads:[~2022-10-31 13:22 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
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 [this message]
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='CALDnm52vmVRgcqX0Qv3MUU60KyoTz2hGDa=u-TB+v-xXjxkmPw@mail.gmail.com' \
--to=joaotavora@gmail.com \
--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).