From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: mekeor@posteo.de, 62687@debbugs.gnu.org
Subject: bug#62687: [PATCH] Eglot: eglot--sig-info: Show SigInfo Docs if Markup; fix regex for highlighting; etc
Date: Tue, 11 Apr 2023 16:59:32 +0300 [thread overview]
Message-ID: <83h6tma5a3.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm53inhy5Gg5uzPV3EhXaHT+xc-9xq--o5iMY5Ua03=WXpQ@mail.gmail.com> (message from João Távora on Tue, 11 Apr 2023 14:53:11 +0100)
> Cc: 62687@debbugs.gnu.org
> From: João Távora <joaotavora@gmail.com>
> Date: Tue, 11 Apr 2023 14:53:11 +0100
>
> I will say, though, that some of these ElDoc mechanisms are somewhat
> poorly documented in the Emacs manual. So if you have time and energy
> on your hands, writing an ElDoc manual (separate section, same
> section, or even separate manual -- Eli is the person to contact
> about that), is a worthy endeavor IMO.
Yes, ElDoc's documentation "needs work". It originally documented
only its support for Lisp, so lots of later-added functionality is not
yet documented well enough.
next prev parent reply other threads:[~2023-04-11 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 21:17 bug#62687: 30.0.50; Eglot (eglot--sig-info): SignatureInformation's Documentation is never shown when it's of type MarkupContent Mekeor Melire
2023-04-06 19:21 ` Mekeor Melire
2023-04-06 19:49 ` Mekeor Melire
2023-04-06 20:34 ` Mekeor Melire
2023-04-07 22:40 ` bug#62687: [PATCH] Eglot: eglot--sig-info: Show SigInfo Docs if Markup; fix regex for highlighting; etc Mekeor Melire
2023-04-07 23:49 ` João Távora
2023-04-07 23:53 ` João Távora
2023-04-08 14:35 ` Mekeor Melire
2023-04-08 19:47 ` João Távora
2023-04-08 20:44 ` Mekeor Melire
2023-04-08 21:12 ` João Távora
2023-04-08 22:31 ` João Távora
2023-04-09 21:46 ` Mekeor Melire
2023-04-10 7:14 ` João Távora
2023-04-10 20:02 ` Mekeor Melire
2023-04-11 11:16 ` João Távora
2023-04-11 11:47 ` Mekeor Melire
2023-04-11 12:56 ` João Távora
2023-04-11 13:53 ` João Távora
2023-04-11 13:59 ` Eli Zaretskii [this message]
2023-04-09 22:14 ` Mekeor Melire
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=83h6tma5a3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62687@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=mekeor@posteo.de \
/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.