From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: John Yates <john@yates-sheets.org>,
"Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>,
emacs-devel@gnu.org
Subject: Re: Question on set-window-margins
Date: Thu, 4 Jan 2024 16:25:26 -0800 [thread overview]
Message-ID: <AEE7BB0E-14E2-45F1-B882-433C3AACF228@gmail.com> (raw)
In-Reply-To: <83ttntw9a6.fsf@gnu.org>
> On Jan 4, 2024, at 4:52 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: John Yates <john@yates-sheets.org>
>> Date: Thu, 4 Jan 2024 07:29:00 -0500
>> Cc: nicolas.rougier@inria.fr, casouri@gmail.com, emacs-devel@gnu.org
>>
>> On Wed, Jan 3, 2024 at 11:49 AM Eli Zaretskii <eliz@gnu.org> wrote:
>>>
>>> We do that when there are too many details to have them in the doc
>>> string. Otherwise, there's no need for a link because typing 'i' in
>>> the *Help* buffer will show the corresponding documentation in the
>>> manual.
>>
>> A visual link has the virtue that it makes immediately clear case
>> holds.
>
> It is infeasible to maintain such a link in a doc string of every
> symbol which is described in the manual(s), and unreasonable to expect
> us to add a link to each doc string of such symbols. There are too
> many of them, and keeping the links up-to-date given the changes in
> the manuals is a lot of work. So we do that judiciously, where we
> think it's needed; a judgment call.
Helpful.el automatically inserts a button that links to the manual entry if it can find the symbol in the manual. It’s probably not perfect, but I frequently found it to be, well, helpful ;-)
The test function is defined as
(defun helpful--in-manual-p (sym)
"Return non-nil if SYM is in an Info manual."
(let ((completions
(cl-letf (((symbol-function #'message)
(lambda (_format-string &rest _args))))
(info-lookup->completions 'symbol 'emacs-lisp-mode))))
(-when-let (buf (get-buffer " temp-info-look"))
(kill-buffer buf))
(or (assoc sym completions)
(assoc-string sym completions))))
Yuan
next prev parent reply other threads:[~2024-01-05 0:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:58 Question on set-window-margins Nicolas P. Rougier (inria)
2024-01-02 19:20 ` Eli Zaretskii
2024-01-02 19:46 ` Nicolas P. Rougier (inria)
2024-01-03 3:23 ` Eli Zaretskii
2024-01-03 3:42 ` Yuan Fu
2024-01-03 5:50 ` Nicolas P. Rougier (inria)
2024-01-03 13:15 ` Eli Zaretskii
2024-01-03 14:05 ` Nicolas P. Rougier (inria)
2024-01-03 16:46 ` Eli Zaretskii
2024-01-03 17:24 ` Nicolas P. Rougier (inria)
2024-01-03 17:28 ` Eli Zaretskii
2024-01-03 17:56 ` Nicolas P. Rougier (inria)
2024-01-03 21:52 ` Jeremy Bryant
2024-01-04 8:53 ` Nicolas P. Rougier (inria)
2024-01-03 15:11 ` John Yates
2024-01-03 16:49 ` Eli Zaretskii
2024-01-03 20:07 ` [External] : " Drew Adams
2024-01-04 12:29 ` John Yates
2024-01-04 12:52 ` Eli Zaretskii
2024-01-05 0:25 ` Yuan Fu [this message]
2024-01-05 8:01 ` Eli Zaretskii
2024-01-06 4:35 ` Richard Stallman
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=AEE7BB0E-14E2-45F1-B882-433C3AACF228@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=nicolas.rougier@inria.fr \
/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).