all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Michael Albinus <michael.albinus@gmx.de>,
	"58602@debbugs.gnu.org" <58602@debbugs.gnu.org>
Cc: "michael_heerdegen@web.de" <michael_heerdegen@web.de>
Subject: bug#58602: 29.0.50; Please document (:documentation FORM) spec for closures
Date: Thu, 20 Oct 2022 16:50:44 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488E069CF404BD2073C69EDF32A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87ilkeg7mo.fsf@gmx.de>

> 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 :-)

1. We _can_ have index entries that start with
`:', and we do have some.  E.g., these `Key
(Character) Index' entries in the Emacs manual:

 * :d (Dired): Operating on Files.  (line 124)
 * :e (Dired): Operating on Files.  (line 136)
 * :s (Dired): Operating on Files.  (line 132)
 * :v (Dired): Operating on Files.  (line 128)

And _if you go to that index_ you can follow
those entries to their nodes, with no problem.

And we have command `info-apropos', which
checks all indexes of all manuals.  And with
that you can input a string that starts with
`:', and you can get to the locations targeted
by such entries with no problem.

The problem is only (?) with `i' (`Info-index').
With that you can type, say, `:d TAB', which
correctly shows you the completion `:d (Dired)'.

But choosing that completion takes you to the
wrong node - it finds 5 matches for `d (Dired)',
instead of one match for `:d (Dired)'.  (It does
find the desired match, but mixed in with other
noise - non-matches.)

2. If we can't fix this directly, then what
Michael A. says maybe points to a workaround
that Emacs could provide.

Many (most?) users won't have a clue about this 
difficulty of using `i' with index entries that
start with `:'.  And they won't understand
what's going on.

What we could do, is to tell a user, when s?he
tries to use `i' with a name that starts with
`:', that `i' only searches for index entries
with that name _minus_ the `:'.  We could then
suggest that s?he use `C-s :<whatever>' instead.

IOW, if this defect of our Info interface isn't
directly fixable then we might at least let
users know that (1) they can't reasonably use
`i :' and (2) they can at least use `C-s :' as
a workaround.





      reply	other threads:[~2022-10-20 16:50 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
2022-10-20 16:50               ` Drew Adams [this message]

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=SJ0PR10MB5488E069CF404BD2073C69EDF32A9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=58602@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --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 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.