From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-pretest-bug@gnu.org
Subject: bug#1550: 23.0.60; bad help xref or bad info installation?
Date: Fri, 12 Dec 2008 15:30:48 +0100 [thread overview]
Message-ID: <874p19xy7b.fsf@escher.local.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
In GNU Emacs 23.0.60.23 (i686-pc-linux-gnu, GTK+ Version 2.12.9)
of 2008-12-12 on escher
1. emacs -Q
2. C-h f declare-function RET
3. Click or type RET on the link `elisp(Declaring Functions)' at the
end of the *Help* buffer, to visit the Elisp info file.
==>
Emacs signals the error "byte-code: No such node or anchor:
elisp(Declaring Functions)" and the *Help* buffer switches to an *info*
buffer containing the raw text of /usr/local/info/emacs (not elisp!).
This buffer is in Info-mode but it is wholely unpropertized and the
header line is present but empty.
This is completely reproducible. However, when I enable debug-on-error
and repeat the above steps, it does not generate a backtrace, despite
signalling the error. (Why? Is this a (different) bug?) But when I
then immediately switch from the raw *info* buffer back to the *Help*
buffer again and type RET on the link, I get another error, with the
following backtrace (but only if I do not kill the *info* buffer):
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: backtrace --]
[-- Type: text/plain, Size: 890 bytes --]
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match("\\([^.]+\\)\\." nil)
byte-code("Æ\b!1
Info-find-node-2("/usr/local/info/emacs" nil t)
Info-find-node("/usr/local/info/emacs" nil t)
byte-code("\b!
signal(error ("No such node or anchor: elisp(Declaring Functions)"))
error("No such node or anchor: %s" "elisp(Declaring Functions)")
byte-code("Æ\b!1
Info-find-node-2("/usr/local/info/emacs" "elisp(Declaring Functions)" nil)
Info-find-node("emacs" "elisp(Declaring Functions)")
Info-goto-node("(emacs)elisp(Declaring Functions)")
info("(emacs)elisp(Declaring Functions)")
apply(info "(emacs)elisp(Declaring Functions)")
help-do-xref(1624 info ("(emacs)elisp(Declaring Functions)"))
help-button-action(#<marker (moves after insertion) at 1632 in *Help*>)
push-button(1632)
call-interactively(push-button nil nil)
[-- Attachment #3: Type: text/plain, Size: 878 bytes --]
I have no idea what's going on here, but it may be related to something
else I recently noticed. My installed dir file in /usr/local/share/info
contains lots of lines like the following scattered throughout the file
(these lines are not in the dir file in the Emacs source directory):
This is ../../info/eintr, produced by makeinfo version 4.11 from emacs-lisp-intro.texi.
This is ../../info/sasl, produced by makeinfo version 4.11 from sasl.texi.
This is ../../info/remember, produced by makeinfo version 4.11 from remember.texi.
I don't know when these lines appeared, but I think it wasn't too long
ago. Does anyone know what caused this? FWIW, the Makefile installs
the Emacs Info files and dir in /usr/local/share/info, and I symlink
these to /usr/local/info, but I've been doing that for a long time and
I'm pretty sure the above lines are of more recent vintage.
next reply other threads:[~2008-12-12 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 14:30 Stephen Berman [this message]
2008-12-12 14:49 ` bug#1550: 23.0.60; bad help xref or bad info installation? Andreas Schwab
2008-12-12 19:15 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874p19xy7b.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=1550@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.