From: Drew Adams <drew.adams@oracle.com>
To: 19918@debbugs.gnu.org
Subject: bug#19918: 25.0.50; links in *Backtrace* & *Help* go to the wrong function definitions
Date: Sat, 21 Feb 2015 16:53:29 -0800 (PST) [thread overview]
Message-ID: <3d4f4b11-14c3-43a2-ab73-45110a21f984@default> (raw)
In my setup, i.e., with Bookmark+ loaded, function `bookmark-bmenu-list'
is defined in file bookmark+-bmu.el. In the debugger, there is a line
like this:
* bookmark-bmenu-list(nil)
with the function name highlighted with a button. `C-u C-x =' on the
name shows this:
Here is a `help-function-def' button labeled `bookmark-bmenu-list'.
There are text properties here:
button (t)
category help-function-def-button
help-args [Show]
Clicking [Show] shows this:
(bookmark-bmenu-list
"d:/Emacs-25-2014-10-20/share/emacs/25.0.50/lisp/bookmark.el")
That's wrong. And clicking mouse-2 on that button takes me to that
wrong file. And so does `C-h f' followed by the name and clicking on
the library, which is shown as bookmark.el.
The debugger correctly traverses the code of the version of the function
that is defined in bookmark+-bmu.el, however.
IOW, the function is defined correctly. It is only the links in Help
and the debugger that are wrong, as well as the file name in Help. But
the doc string in Help is correct - it is the doc string for the
Bookmark+ version of the function.
The redefinition of the function in bookmark+-bmu.el is a
straightforward defun.
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-02-22 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 0:53 Drew Adams [this message]
2016-04-30 17:09 ` bug#19918: 25.0.50; links in *Backtrace* & *Help* go to the wrong function definitions Lars Ingebrigtsen
2016-04-30 18:03 ` Drew Adams
2019-12-01 8:18 ` Stefan Kangas
2019-12-01 17:44 ` Drew Adams
2019-12-01 21:57 ` Stefan Kangas
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=3d4f4b11-14c3-43a2-ab73-45110a21f984@default \
--to=drew.adams@oracle.com \
--cc=19918@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).