unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eshel Yaron <me@eshelyaron.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
	 goncholden <goncholden@protonmail.com>,
	 "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Documentation by function beyond elisp
Date: Fri, 10 Mar 2023 16:50:29 +0200	[thread overview]
Message-ID: <m1lek4u0cq.fsf@gmail.com> (raw)
In-Reply-To: <CAP_d_8X+qs08MKqeqjkF-924Aoc0a8z=t23LkuMNuiORJFjH6A@mail.gmail.com> (Yuri Khan's message of "Fri, 10 Mar 2023 17:23:41 +0700")

Yuri Khan <yuri.v.khan@gmail.com> writes:

> On Fri, 10 Mar 2023 at 16:12, Ihor Radchenko <yantar92@posteo.net> wrote:
>>
>> Yuri Khan <yuri.v.khan@gmail.com> writes:
>>
>> > For languages other than Elisp, this is handled by the language
>> > server. Eglot arranges for language-server-provided function help to
>> > be displayed by ElDoc.
>>
>> What about an equivalent of the *Help* buffer?
>
> Well, what about it? You move the point to an identifier. Its
> signature and a few lines of documentation are shown in the echo area.
> You invoke (eldoc-doc-buffer) and see the whole documentation.
>
> It may be a bit inconvenient that the content of that buffer changes
> as you move point to a different identifier. But that can be worked
> around with (clone-buffer).

IMO ElDoc and Help and two pretty different features, each with its own
use and purpose.  Eglot integrates with ElDoc but not with Help AFAIU,
but language-specific packages can (and should!) integrate with both of
these facilities.  Emacs lets package authors reuse the Help UI pretty
easily.  For example, my package sweeprolog.el (for working with
SWI-Prolog code) provides both ElDoc integration and a command
sweeprolog-describe-predicate that works much like describe-predicate,
it uses the help.el interface to show a proper *Help* buffer with the
documentation of a given Prolog predicate.  References to other
predicates become links to their corresponding *Help* buffers, just like
we have for Elisp.  It even works for user-defined predicates.


Cheers,
Eshel



  parent reply	other threads:[~2023-03-10 14:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 11:33 Documentation by function beyond elisp goncholden
2023-03-09 12:07 ` Po Lu
2023-03-09 12:17   ` goncholden
2023-03-09 13:33     ` Po Lu
2023-03-09 13:58       ` goncholden
2023-03-09 12:24 ` Eli Zaretskii
2023-03-09 13:01   ` goncholden
2023-03-09 15:29     ` Eli Zaretskii
2023-03-09 15:36       ` goncholden
2023-03-09 15:48     ` Eli Zaretskii
2023-03-09 17:04       ` goncholden
2023-03-09 17:33         ` Eli Zaretskii
2023-03-09 15:50 ` Yuri Khan
2023-03-10  9:14   ` Ihor Radchenko
2023-03-10 10:23     ` Yuri Khan
2023-03-10 14:43       ` João Távora
2023-03-10 14:50       ` Eshel Yaron [this message]
2023-03-10 15:33         ` João Távora
2023-03-11 10:46         ` Augusto Stoffel
2023-03-11 19:04           ` Eshel Yaron

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=m1lek4u0cq.fsf@gmail.com \
    --to=me@eshelyaron.com \
    --cc=emacs-devel@gnu.org \
    --cc=goncholden@protonmail.com \
    --cc=yantar92@posteo.net \
    --cc=yuri.v.khan@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).