From: Augusto Stoffel <arstoffel@gmail.com>
To: Eshel Yaron <me@eshelyaron.com>
Cc: Yuri Khan <yuri.v.khan@gmail.com>,
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: Sat, 11 Mar 2023 11:46:15 +0100 [thread overview]
Message-ID: <877cvnr2fc.fsf@gmail.com> (raw)
In-Reply-To: <m1lek4u0cq.fsf@gmail.com> (Eshel Yaron's message of "Fri, 10 Mar 2023 16:50:29 +0200")
On Fri, 10 Mar 2023 at 16:50, Eshel Yaron wrote:
> 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,
Right, the LSP protocol doesn't have an interface for anything like
`C-h o'. You only get information on the symbol at point.
> 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.
The generic Emacs way to provide this functionality is the Info symbol
lookup command `C-h S'. If your language doesn't have an Info manual
you may have better luck with the `devdocs' package (which I mention as
a shameless but pertinent plug).
Out of curiosity: apart from the issue of availability of documentation
in different formats, is there any prolog-specific logic in
sweeprolog-describe-predicate?
next prev parent reply other threads:[~2023-03-11 10:46 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
2023-03-10 15:33 ` João Távora
2023-03-11 10:46 ` Augusto Stoffel [this message]
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=877cvnr2fc.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=goncholden@protonmail.com \
--cc=me@eshelyaron.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).