From: Michael Albinus <michael.albinus@gmx.de>
To: 58602@debbugs.gnu.org
Cc: michael_heerdegen@web.de
Subject: bug#58602: 29.0.50; Please document (:documentation FORM) spec for closures
Date: Thu, 20 Oct 2022 11:35:27 +0200 [thread overview]
Message-ID: <87ilkeg7mo.fsf@gmx.de> (raw)
In-Reply-To: <87y1tb75z9.fsf@web.de> (Michael Heerdegen's message of "Thu, 20 Oct 2022 01:23:38 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
Hi,
>> > [...] I noticed that `i :documentation RET` doesn't bring me to this
>> > text, instead it just looks for "documentation"
>
>> `Info-index':
>> ;; Strip leading colon in topic; index format does not allow them.
>> (if (and (stringp topic)
>> (> (length topic) 0)
>> (= (aref topic 0) ?:))
>> (setq topic (substring topic 1)))
>
> Yes, deleting that part breaks the i command, so I guess we have to live
> with this restriction or find a way to filter out the wanted matches.
I prefer searching in info via 's', like 's :documentation RET'. This
has also the advantage over the 'i' command to show me dark corners of a
manual which haven't been indexed properly :-)
> Michael.
Best regards, Michael.
next prev parent reply other threads:[~2022-10-20 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 0:46 bug#58602: 29.0.50; Please document (:documentation FORM) spec for closures Michael Heerdegen
2022-10-18 2:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 2:20 ` Christopher Dimech
2022-10-18 3:16 ` Michael Heerdegen
2022-10-18 13:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 20:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 20:39 ` Drew Adams
2022-10-19 1:24 ` Michael Heerdegen
2022-10-19 23:23 ` Michael Heerdegen
2022-10-20 9:35 ` Michael Albinus [this message]
2022-10-20 16:50 ` Drew Adams
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=87ilkeg7mo.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=58602@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).