From: "T.V Raman" <raman@google.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: info-lookup-alist mangled, breaks C-h S
Date: Wed, 05 Jan 2022 09:33:12 -0800 [thread overview]
Message-ID: <p91fsq25bqf.fsf@google.com> (raw)
In-Reply-To: <87tueidwo3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 05 Jan 2022 16:33:48 +0100")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 884 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
I still wonder whether the complex list surgery performed by modules
like tramp-integration is truly needed in current Emacs, or if it's a
throw-back from the distant past that has been amplified by
copy/paste/edit cycles.
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> +(mapc
>> + (lambda (elem)
>> + (let* ((prefix (car elem)))
>> + (info-lookup-add-help
>> + :mode (cons 'emacs-lisp-mode prefix) <<<<<<<<<<<<<<<<<
>>
>> Now HELP-MODE could be a cons cell, not just a symbol. But the doc
>> string of info-lookup-alist was not updated, and therefore the
>> semantics of this form is not documented. What does that cons cell
>> value mean?
>
> The doc string change you've done looks correct to me.
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2022-01-05 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 16:52 info-lookup-alist mangled, breaks C-h S T.V Raman
2022-01-03 10:35 ` Daniel Martín
2022-01-03 14:45 ` T.V Raman
2022-01-03 20:02 ` Tassilo Horn
2022-01-04 14:54 ` Eli Zaretskii
2022-01-04 15:03 ` Eli Zaretskii
2022-01-05 15:33 ` Lars Ingebrigtsen
2022-01-05 16:46 ` Eli Zaretskii
2022-01-05 17:33 ` T.V Raman [this message]
2022-01-04 16:19 ` Tassilo Horn
2022-01-04 16:27 ` T.V Raman
2022-01-04 16:46 ` Eli Zaretskii
2022-01-05 13:18 ` Eli Zaretskii
2022-01-04 15:45 ` T.V Raman
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=p91fsq25bqf.fsf@google.com \
--to=raman@google.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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.