GNU bug report logs - #7941
24.0.50; Compilation mode broken, next-error not working

Previous Next

Package: emacs;

Reported by: Jan Djärv <jan.h.d <at> swipnet.se>

Date: Sun, 30 Jan 2011 13:49:02 UTC

Severity: normal

Found in version 24.0.50

Done: Stefan Monnier <monnier <at> iro.umontreal.ca>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 7941 in the body.
You can then email your comments to 7941 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#7941; Package emacs. (Sun, 30 Jan 2011 13:49:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jan Djärv <jan.h.d <at> swipnet.se>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 30 Jan 2011 13:49:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.0.50; Compilation mode broken, next-error not working
Date: Sun, 30 Jan 2011 14:56:47 +0100
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your report will be posted to the bug-gnu-emacs <at> gnu.org mailing list
and the gnu.emacs.bug news group, and at http://debbugs.gnu.org.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug.  If you can, give
a recipe starting from `emacs -Q':

(setq compilation-scroll-output t)
M-x compile (somewhere where you get warnings or errors).
M-x next-error
compilation-next-error-function: Wrong type argument: arrayp, nil

M-x compile
run-hooks: Wrong type argument: number-or-marker-p, nil


A second compile doesn't work until I kill the *compilation* buffer.
next-error never works.

Can the "compilation--flush-parse: 1 16056" messages be turned off?

           Jan D.

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'.
For information about debugging Emacs, please read the file
/Users/jhd/src/emacs/current/nextstep/Emacs.app/Contents/Resources/etc/DEBUG.


In GNU Emacs 24.0.50.11 (x86_64-apple-darwin10.6.0, NS apple-appkit-1038.35)
 of 2011-01-30 on zeplin
Windowing system distributor `Apple', version 10.3.1038
configured using `configure  '--verbose' '--enable-asserts' '--with-ns' 
'--without-x' 'CFLAGS=-g''

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: sv_SE.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Fundamental

Minor modes in effect:
  tooltip-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-y <up> <up> C-a ( s e t q SPC C-w C-_ C-e C-j <escape>
x c o m p i l e <return> <return> <escape> x n e x
t - e r r o r <return> <escape> x <up> <up> <return>
<return> C-x b <return> <escape> x r e p o r t - e
m <tab> <return>

Recent messages:
compilation--flush-parse: 16012 16012
compilation--flush-parse: 16023 16023
compilation--flush-parse: 16024 16024
compilation--flush-parse: 16032 16032
compilation--flush-parse: 16036 16036
compilation--flush-parse: 16011 16056
Compilation finished
compilation-next-error-function: Wrong type argument: arrayp, nil
(No files need saving)
compilation--flush-parse: 1 16056
run-hooks: Wrong type argument: number-or-marker-p, nil

Load-path shadows:
None found.

Features:
(shadow sort gnus-util time-date mail-extr message rfc822 mml easymenu
mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mailabbrev mail-utils gmm-utils mailheader
emacsbug compile comint regexp-opt ring tooltip ediff-hook vc-hooks
lisp-float-type mwheel ns-win tool-bar dnd fontset image fringe
lisp-mode register page menu-bar rfn-eshadow timer select scroll-bar
mouse jit-lock font-lock syntax facemenu font-core frame cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev
loaddefs button minibuffer faces cus-face files text-properties overlay
md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process ns multi-tty
emacs)




Reply sent to Stefan Monnier <monnier <at> iro.umontreal.ca>:
You have taken responsibility. (Tue, 01 Feb 2011 16:28:01 GMT) Full text and rfc822 format available.

Notification sent to Jan Djärv <jan.h.d <at> swipnet.se>:
bug acknowledged by developer. (Tue, 01 Feb 2011 16:28:01 GMT) Full text and rfc822 format available.

Message #10 received at 7941-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Jan Djärv <jan.h.d <at> swipnet.se>
Cc: 7941-done <at> debbugs.gnu.org
Subject: Re: bug#7941: 24.0.50; Compilation mode broken, next-error not working
Date: Tue, 01 Feb 2011 11:35:26 -0500
> (setq compilation-scroll-output t)
> M-x compile (somewhere where you get warnings or errors).
> M-x next-error
> compilation-next-error-function: Wrong type argument: arrayp, nil

Thanks, I just installed the patch below which should fix it.

> M-x compile
> run-hooks: Wrong type argument: number-or-marker-p, nil

I believe I've fixed this one yesterday or so.

> Can the "compilation--flush-parse: 1 16056" messages be turned off?

No, of course not, they're crucial for the user.


        Stefan "just kidding"


=== modified file 'lisp/ChangeLog'
--- lisp/ChangeLog	2011-02-01 10:12:25 +0000
+++ lisp/ChangeLog	2011-02-01 16:31:01 +0000
@@ -1,3 +1,8 @@
+2011-02-01  Stefan Monnier  <monnier <at> iro.umontreal.ca>
+
+	* progmodes/compile.el (compilation-next-error): Check there's
+	a message before using it (bug#7941).
+
 2011-02-01  Jay Belanger  <jay.p.belanger <at> gmail.com>
 
 	* calc/calc-mtx.el (math-lud-pivot-check): New function.
@@ -6,8 +11,8 @@
 
 2011-01-31  Alan Mackenzie  <acm <at> muc.de>
 
-	* progmodes/cc-cmds.el (c-forward-over-illiterals): Continue
-	parsing if we encounter a naked # (Bug#7595).
+	* progmodes/cc-cmds.el (c-forward-over-illiterals):
+	Continue parsing if we encounter a naked # (Bug#7595).
 	(c-beginning-of-statement): Avoid loop in locating the beginning
 	of a macro.
 
@@ -34,8 +39,8 @@
 
 2011-01-31  Kenichi Handa  <handa <at> m17n.org>
 
-	* international/quail.el (quail-keyboard-layout-alist): Remove
-	superfluous SPC for "pc105-uk" (bug#7927).
+	* international/quail.el (quail-keyboard-layout-alist):
+	Remove superfluous SPC for "pc105-uk" (bug#7927).
 
 2011-01-31  Glenn Morris  <rgm <at> gnu.org>
 

=== modified file 'lisp/progmodes/compile.el'
--- lisp/progmodes/compile.el	2011-01-31 17:11:11 +0000
+++ lisp/progmodes/compile.el	2011-02-01 16:28:10 +0000
@@ -2140,7 +2140,7 @@
   (or pt (setq pt (point)))
   (let* ((msg (get-text-property pt 'compilation-message))
          ;; `loc', `msg', and `last' are used by the compilation-loop macro.
-	 (loc (compilation--message->loc msg))
+	 (loc (and msg (compilation--message->loc msg)))
 	 last)
     (if (zerop n)
 	(unless (or msg			; find message near here
@@ -2154,8 +2154,7 @@
 						  (line-end-position)))
 	    (or (setq msg (get-text-property pt 'compilation-message))
 		(setq pt (point)))))
-      (setq last (compilation--loc->file-struct
-                  (compilation--message->loc msg)))
+      (setq last (compilation--loc->file-struct loc))
       (if (>= n 0)
 	  (compilation-loop > compilation-next-single-property-change 1-
 			    (if (get-buffer-process (current-buffer))





Information forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#7941; Package emacs. (Wed, 02 Feb 2011 19:15:02 GMT) Full text and rfc822 format available.

Message #13 received at 7941 <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 7941 <at> debbugs.gnu.org
Subject: Re: bug#7941: 24.0.50; Compilation mode broken, next-error not working
Date: Wed, 02 Feb 2011 20:22:40 +0100

Stefan Monnier skrev 2011-02-01 17.35:
>> (setq compilation-scroll-output t)
>> M-x compile (somewhere where you get warnings or errors).
>> M-x next-error
>> compilation-next-error-function: Wrong type argument: arrayp, nil
>
> Thanks, I just installed the patch below which should fix it.

Confirmed, thanks.

	Jan D.





bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Thu, 03 Mar 2011 12:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 14 years and 171 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.