From: "João Távora" <joaotavora@gmail.com>
To: Mekeor Melire <mekeor@posteo.de>
Cc: 62687@debbugs.gnu.org
Subject: bug#62687: [PATCH] Eglot: eglot--sig-info: Show SigInfo Docs if Markup; fix regex for highlighting; etc
Date: Sat, 08 Apr 2023 20:47:41 +0100 [thread overview]
Message-ID: <87cz4egnqa.fsf@gmail.com> (raw)
In-Reply-To: <DA250478-C947-4F25-AB21-0CA336AD9A9E@posteo.de> (Mekeor Melire's message of "Sat, 08 Apr 2023 14:35:40 +0000")
Mekeor Melire <mekeor@posteo.de> writes:
>>You wrote 5 long messages back to back in this bug, reporting
>>multiple issues and bugs and wishes. I'm not one to request
>>TL;DR or executive summaries usually, but here I must, as I
>>am a single threaded person.
>>
>>Can you try to summarize the main issue in less than 20 lines?
>>Else, I'm going to find it very hard to be able to help you.
>
> The main issue is that Eglot won't show the "SignatureInformation"'s
> "documentation" field if it is of type MarkupContent.
OK I see it, I understand it, and I've done some changes to master.
Please have a look at commit 685435cb52eaa6f61b7088398f1f53e69d76e63e.
Note that the general principle here is that the echo area gets as few
lines as possible, and the *eldoc* buffer gets much more. So it's a
good idea to have the *eldoc* buffer showing somewhere (which you can
summon with 'C-h .').
> If you want, I can create separate bug reports for the other bugs I
> found in the eglot--sig-info function.
Let's focus on this "main issue" before we move on to others.
> But I think my last e-mail was quite concise.
The problem is you wrote 5 of them :-) Should I just focus on your last
email and ignore the others, then? If so what exactly is the debbugs
link for this last "concise" email?
João
next prev parent reply other threads:[~2023-04-08 19:47 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 [this message]
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
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=87cz4egnqa.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=62687@debbugs.gnu.org \
--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.