From: "Drew Adams" <drew.adams@oracle.com>
To: 12737@debbugs.gnu.org
Subject: bug#12737: 24.2.50; `help-xref-interned' should not put point on last doc section
Date: Thu, 25 Oct 2012 14:47:38 -0700 [thread overview]
Message-ID: <0D88849F49BF48389C49B1F89E4BACA4@us.oracle.com> (raw)
`help-xref-interned' provides a help page that includes all of the
available doc for a symbol: function, variable, and face - whatever is
available.
The doc is presented in this order: function, face, var (or function,
face, if no var doc).
Currently point is placed on the last doc section: the var section (or
the face section if no var). This is wrong, IMO. Point should be
placed at bob. If it's not clear at bob that there is more than one
kind of doc present, then the header should be modified to make this
clear, and it should have links to each section.
It is disorienting for a user to follow a link and find himself near the
end of a doc page with no indication of what the page documents overall.
In GNU Emacs 24.2.50.1 (i386-mingw-nt5.1.2600)
of 2012-10-22 on DANI-PC
Bzr revision: 110618 monnier@iro.umontreal.ca-20121022132928-232zm0fecassmhfb
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-I../../libs/libxpm-3.5.8/include -I../../libs/libxpm-3.5.8/src
-I../../libs/libpng-1.4.10 -I../../libs/zlib-1.2.6
-I../../libs/giflib-4.1.4-1/include -I../../libs/jpeg-6b-4/include
-I../../libs/tiff-3.8.2-1/include
-I../../libs/libxml2-2.7.8-w32-bin/include/libxml2
-I../../libs/gnutls-3.0.16/include
-I../../libs/libiconv-1.14-2-mingw32-dev/include'
next reply other threads:[~2012-10-25 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 21:47 Drew Adams [this message]
2012-11-17 6:49 ` bug#12737: 24.2.50; `help-xref-interned' should not put point on last doc section Chong Yidong
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=0D88849F49BF48389C49B1F89E4BACA4@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12737@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).