GNU bug report logs -
#1930
23.0.60; Can't jump to error location in compilation-mode
Previous Next
Reported by: Magnus Henoch <mange <at> freemail.hu>
Date: Fri, 16 Jan 2009 14:50:03 UTC
Severity: normal
Merged with 1929
Done: martin rudalics <rudalics <at> gmx.at>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Fri, 16 Jan 2009 17:59:34 +0100
with message-id <4970BCF6.7000407 <at> gmx.at>
and subject line Re: bug#1930: 23.0.60; Can't jump to error location in compilation-mode
has caused the Emacs bug report #1930,
regarding 23.0.60; Can't jump to error location in compilation-mode
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact help-debbugs <at> gnu.org
immediately.)
--
1930: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1930
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
After running a compilation with M-x compile, I try to jump to the
location of an error with M-g M-n. This doesn't work, though:
Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
select-window(nil nil)
pop-to-buffer(#<buffer erltest> other-window)
compilation-goto-locus(#<marker at 3465 in *compilation*> #<marker at 1749 in erltest> nil)
compilation-next-error-function(1 nil)
next-error(nil)
call-interactively(next-error nil nil)
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/local/share/emacs/23.0.60/etc/DEBUG for instructions.
In GNU Emacs 23.0.60.4 (i686-pc-linux-gnu, GTK+ Version 2.12.9)
of 2009-01-15 on linux-b2a3
Windowing system distributor `The X.Org Foundation', version 11.0.10400090
configured using `configure '--enable-maintainer-mode''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: C
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US.UTF-8
value of $XMODIFIERS: @im=local
locale-coding-system: utf-8-unix
default-enable-multibyte-characters: t
Major mode: Compilation
Minor modes in effect:
diff-auto-refine-mode: t
jabber-activity-mode: t
jabber-mode-line-mode: t
show-paren-mode: t
server-mode: t
iswitchb-mode: t
icomplete-mode: t
display-time-mode: t
tooltip-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
global-auto-composition-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
line-number-mode: t
transient-mark-mode: t
Recent messages:
Back to top level.
Entering debugger...
Back to top level.
Entering debugger...
Back to top level.
(No files need saving)
Compilation exited abnormally with code 2
Entering debugger...
Mark set [2 times]
Back to top level.
[Message part 3 (message/rfc822, inline)]
I hope this is fixed now. Please try again.
Thanks for reporting immediately, martin.
This bug report was last modified 16 years and 129 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.