unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Hong Xu <hong@topbug.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25033@debbugs.gnu.org
Subject: bug#25033: [PATCH] Add a missing index for `man'.
Date: Sat, 26 Nov 2016 11:17:35 -0800	[thread overview]
Message-ID: <87bmx2gieo.fsf@topbug.net> (raw)
In-Reply-To: <83wpfq1nxu.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]


On 2016-11-26 Sat 03:27 GMT-0800, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Hong Xu <hong@topbug.net>
>> Cc: 25033@debbugs.gnu.org
>> Date: Sat, 26 Nov 2016 02:06:02 -0800
>>
>> >> +@findex man
>> >>  @findex manual-entry
>> >>    You can read the man page for an operating system command, library
>> >>  function, or system call, with the @kbd{M-x man} command.  This
>> >
>> > If I type "i man RET" in the current Emacs manual, I land in that
>> > node, and "i man TAB" produces a list of completions one of which is
>> > "man pages", which leads to the same node.  So why did you see the
>> > need for adding this index entry?
>>
>> The missing index actually confused me when I searched the manual for
>> it, as it was hidden in my completion list.
>
> Please describe in more detail how it happened that it was hidden,
> perhaps there's something I'm missing.
>

I use ivy-mode for completion. I was expecting there was an exact
matching of "man", but there wasn't. A lot of other entries with higher
scores were on the first page of the completion list.

>> The main reason is though for the completeness of the documentation --
>> "man" should be an indexed function name just like "manual-entry". I
>> don't see how it could be harmful to add this index, although the
>> benefit may also not be significant.
>
> The harm is in having two or more index entries that begin with the
> same text and point to the same page.  That's not useful, and its only
> effect is bloating the index, including in the printed version of the
> manual (which increases the page count).  So we try to avoid that.

These are two different types of indices: one is a function, the other
is a concept -- they locate in different indices. If a user wants to
look for the man function, it can't be found in the function index.

How about this: replace all "manual-entry" with "man" in the section,
and remove the "manual-entry" index as well. In this way, the total
number of indices won't increase. It also fixes the inconsistency --
both "M-x manual-entry" and "M-x man" are used without pointing out they
are the same thing.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2016-11-26 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  9:18 bug#25033: [PATCH] Add a missing index for `man' Hong Xu
2016-11-26  9:29 ` Eli Zaretskii
2016-11-26 10:06   ` Hong Xu
2016-11-26 11:27     ` Eli Zaretskii
2016-11-26 19:17       ` Hong Xu [this message]
2016-12-02  9:15         ` Eli Zaretskii

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=87bmx2gieo.fsf@topbug.net \
    --to=hong@topbug.net \
    --cc=25033@debbugs.gnu.org \
    --cc=eliz@gnu.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 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).