From: "João Távora" <joaotavora@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: 43205@debbugs.gnu.org
Subject: bug#43205: 28.0.50; Eldoc protocol not useful for third-party packages
Date: Fri, 4 Sep 2020 19:32:30 +0100 [thread overview]
Message-ID: <CALDnm52n8GTrDcqc7qmMD7q2xDiirogMtWwt-QVn1xAQ9u-63A@mail.gmail.com> (raw)
In-Reply-To: <FABC364C-EC0E-4535-88A2-CA1FD39CC217@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Acknowledged. The latest eldoc in master is a work in progress.This in on
my to-do list. Soon I'll improve the documentation, as well as specifying
what the "display engine" is supposed to be.
I think, this will be quite useful when (re) designing your eldoc-box
extension, Yuan. Maybe that extension could even be included into Emacs
itself.
João
On Fri, Sep 4, 2020, 17:18 Yuan Fu <casouri@gmail.com> wrote:
> Currently the documentation of `eldoc-documentation-functions' says this:
>
> * `:thing', VALUE is a short string or symbol designating what is
> being reported on. The documentation display engine can elect
> to remove this information depending on space contraints;
>
> without saying what VALUE could be. For someone who want to write a
> frontend to display eldoc signitures, this is useless. For someone who
> want to write a documentation backend for eldoc, this is useless as
> well. I think the protocol should at least specify what VALUE could be
> expected: signature? full-doc? example? links?
>
>
>
> Also contraints is spelled wrong. And on line 705.
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1524 bytes --]
next prev parent reply other threads:[~2020-09-04 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 16:13 bug#43205: 28.0.50; Eldoc protocol not useful for third-party packages Yuan Fu
2020-09-04 18:32 ` João Távora [this message]
2020-09-04 19:03 ` Yuan Fu
2021-06-12 12:31 ` Lars Ingebrigtsen
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=CALDnm52n8GTrDcqc7qmMD7q2xDiirogMtWwt-QVn1xAQ9u-63A@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=43205@debbugs.gnu.org \
--cc=casouri@gmail.com \
/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).