[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Poin
From: |
Drew Adams |
Subject: |
bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong |
Date: |
Sat, 14 Mar 2015 07:46:49 -0700 (PDT) |
> > For `i home TAB' you see these candidates:
> > HOME
> > home directory shorthand
> >
> > In my setup I see also these two, but for some reason I don't see them
> > with `emacs -Q':
> > HOME directory on MS-Windows
> > HOME directory under MS-DOS
>
> I see all 4 of them in "emacs -Q". Not sure why you don't; perhaps
> because your build is very old (but I doubt that).
No, I see only 2, even in this recent build (see end of this message).
> Do you have INFOPATH set in the environment, perhaps?
Nope.
> > In any case, those with the uppercase HOME should presumably not point
> > to node `Moving Point' (and, in particular, to the key `<home>'. That
> > is wrong. Presumably, `HOME' should take you to some information about
> > environment variable `HOME' or at least about the home directory.
>
> I disagree. In general, index searches are deliberately
> case-insensitive. In this particular case, you might assume that
> everyone knows the key is called <home>, but a seasonal reader of the
> manual does not necessarily know that; he could, for example, take
> inspiration from SPC, RET, TAB, etc. We shouldn't fail those users,
> IMO.
I agree about (a) case-insensitive "in general" and (b) users might not
know about `<home>' vs `home' vs `HOME'.
But why is `HOME' capitalized as a candidate if it points to info about
the key? That can only be misleading, I think. I don't think Emacs
ever refers to the key that way (unlike, say, `TAB').
If we have a single `home' or `HOME' entry then we invite such problems.
(If we _must_ have a single such entry, I would expect it to point to
the env var.)
We should have similar treatment for the key and the env var, IMO.
E.g., if we have `home directory shorthand' then the key entry should
be something like `home keyboard key'.
And we don't seem to have any entry currently for the env var (?).
Shouldn't a user be able to find some info about it?
`HOME environment variable', for example.
Anyway, I don't have a brilliant solution. But I noticed a problem.
Maybe you can make some improvement based on this feedback. If not,
feel free to close the bug.
More recent build where I still see only two entries for `home TAB':
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2015-02-27 on LEG570
Repository revision: b2a590d4e3dc692a97c1b53e015b945d84b4b4c7
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --host=i686-pc-mingw32 --enable-checking=yes,glyphs'
Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
Important settings:
value of $LANG: ENU
locale-coding-system: cp1252
Major mode: Info
Minor modes in effect:
tooltip-mode: t
global-eldoc-mode: t
electric-indent-mode: t
mouse-wheel-mode: t
tool-bar-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
buffer-read-only: t
line-number-mode: t
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Making completion list...
Quit [2 times]
Load-path shadows:
None found.
Features:
(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev
gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums mm-util
help-fns mail-prsvr mail-utils info easymenu dired time-date tooltip
eldoc electric uniquify ediff-hook vc-hooks lisp-float-type mwheel
dos-w32 ls-lisp disp-table w32-win w32-vars tool-bar dnd fontset image
regexp-opt fringe tabulated-list newcomment elisp-mode lisp-mode
prog-mode register page menu-bar rfn-eshadow timer select scroll-bar
mouse jit-lock font-lock syntax facemenu font-core frame cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev
minibuffer cl-preloaded nadvice loaddefs button faces cus-face macroexp
files text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote make-network-process
w32notify w32 multi-tty emacs)
Memory information:
((conses 8 187997 47058)
(symbols 32 18506 1)
(miscs 32 52 159)
(strings 16 17991 4941)
(string-bytes 1 413382)
(vectors 8 9953)
(vector-slots 4 396848 6048)
(floats 8 68 277)
(intervals 28 35386 3975)
(buffers 516 15))
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Drew Adams, 2015/03/13
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Eli Zaretskii, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong,
Drew Adams <=
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Eli Zaretskii, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Drew Adams, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Eli Zaretskii, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Drew Adams, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Eli Zaretskii, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Drew Adams, 2015/03/14
- bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong, Drew Adams, 2015/03/14