GNU bug report logs -
#1550
23.0.60; bad help xref or bad info installation?
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 1550 in the body.
You can then email your comments to 1550 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1550
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Stephen Berman <stephen.berman <at> gmx.net>
:
New bug report received and forwarded. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
[Message part 1 (text/plain, inline)]
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):
[Message part 2 (text/plain, attachment)]
[Message part 3 (text/plain, inline)]
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.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1550
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Andreas Schwab <schwab <at> suse.de>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #10 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
Stephen Berman <stephen.berman <at> gmx.net> writes:
> 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.
Bug in makeinfo, fixed in 4.12.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab <at> suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1550
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Andreas Schwab <schwab <at> suse.de>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1550
; Package
emacs
.
Full text and
rfc822 format available.
Message #18 received at 1550 <at> emacsbugs.donarmstrong.com (full text, mbox):
Stephen Berman wrote:
> 3. Click or type RET on the link `elisp(Declaring Functions)' at the
Doc typo. Should read
For more information, see Info node `(elisp)Declaring Functions'."
bug closed, send any further explanations to Stephen Berman <stephen.berman <at> gmx.net>
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> emacsbugs.donarmstrong.com
.
(Sat, 13 Dec 2008 04:30:06 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> emacsbugs.donarmstrong.com
.
(Sat, 10 Jan 2009 15:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 16 years and 225 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.