From: Drew Adams <drew.adams@oracle.com>
To: 20105@debbugs.gnu.org
Subject: bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong
Date: Fri, 13 Mar 2015 19:23:31 -0700 (PDT) [thread overview]
Message-ID: <265aed11-7056-45f2-afbf-1b5f8b3b0a05@default> (raw)
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
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.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2015-03-14 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 2:23 Drew Adams [this message]
2015-03-14 8:25 ` bug#20105: 25.0.50; Emacs manual, `i HOME RET' sends you to `Moving Point', which is wrong Eli Zaretskii
[not found] <<265aed11-7056-45f2-afbf-1b5f8b3b0a05@default>
[not found] ` <<83egos2df6.fsf@gnu.org>
2015-03-14 14:46 ` Drew Adams
2015-03-14 15:26 ` Eli Zaretskii
[not found] ` <<b15373cd-5f12-4dde-b999-d0b54c82aa52@default>
[not found] ` <<834mpn38iu.fsf@gnu.org>
2015-03-14 15:59 ` Drew Adams
2015-03-14 16:15 ` Eli Zaretskii
[not found] ` <<9fe72841-fa75-4bbe-bb92-c14e68e0cd7a@default>
[not found] ` <<83zj7f1rox.fsf@gnu.org>
2015-03-14 16:44 ` Drew Adams
2015-03-14 17:39 ` Eli Zaretskii
2015-03-14 17:41 ` Drew Adams
[not found] <<1cf950ce-96bf-4a06-b104-581af13b6b74@default>
[not found] ` <<83twxn1nsx.fsf@gnu.org>
2015-03-14 17:44 ` 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=265aed11-7056-45f2-afbf-1b5f8b3b0a05@default \
--to=drew.adams@oracle.com \
--cc=20105@debbugs.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).