From: Stefan Kangas <stefankangas@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 58892-done@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Felician Nemeth <felician.nemeth@gmail.com>,
larsi@gnus.org, monnier@iro.umontreal.ca
Subject: bug#58892: 29.0.50; [PATCH] eglot-manual: Open the local info documentation
Date: Fri, 11 Nov 2022 05:05:28 -0800 [thread overview]
Message-ID: <CADwFkm=v0bP3BU1AF4ZCUaKeyQcz2u_g9Hf5paWKqK4YawJNSQ@mail.gmail.com> (raw)
In-Reply-To: <CALDnm52vmVRgcqX0Qv3MUU60KyoTz2hGDa=u-TB+v-xXjxkmPw@mail.gmail.com> ("João Távora"'s message of "Mon, 31 Oct 2022 13:22:56 +0000")
João Távora <joaotavora@gmail.com> writes:
> 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.
Now done, see commit c64d94c849.
prev parent reply other threads:[~2022-11-11 13:05 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
2022-10-31 13:36 ` Eli Zaretskii
2022-11-11 13:05 ` Stefan Kangas [this message]
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='CADwFkm=v0bP3BU1AF4ZCUaKeyQcz2u_g9Hf5paWKqK4YawJNSQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=58892-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=joaotavora@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 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.