bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1929: marked as done (23.0.60; compile-goto-error gives "pop-to-buf


From: Emacs bug Tracking System
Subject: bug#1929: marked as done (23.0.60; compile-goto-error gives "pop-to-buffer: Wrong type argument: window-live-p, nil" error)
Date: Fri, 16 Jan 2009 17:05:06 +0000

Your message dated Fri, 16 Jan 2009 17:58:29 +0100
with message-id <address@hidden>
and subject line Re: bug#1929: 23.0.60; compile-goto-error gives 
"pop-to-buffer: Wrong type argument:   window-live-p, nil" error
has caused the Emacs bug report #1929,
regarding 23.0.60; compile-goto-error gives "pop-to-buffer: Wrong type 
argument: window-live-p, nil" error
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 address@hidden
immediately.)


-- 
1929: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1929
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.0.60; compile-goto-error gives "pop-to-buffer: Wrong type argument: window-live-p, nil" error Date: Fri, 16 Jan 2009 14:57:00 +0200
'compile-goto-error' results in the

    "pop-to-buffer: Wrong type argument: window-live-p, nil"

error if appropriate file is not loaded or loaded, but appropriate
buffer is not visible in the same frame where '*compilation*' buffer
lies.

Sources obtained from CVS today, Fri, 16 Jan 2009 12:50 (GMT), but
first time reproduced with yesterday's checkout.  Previous checkout
was far ago in paste (and definitelly in the 2008 year), therefore, I
unable to say exact time of the problematic commit :-(

Lisp Backtrace:
Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
  select-window(nil nil)
  pop-to-buffer(#<buffer z.c> other-window)
  compilation-goto-locus(#<marker at 204 in *compilation*> #<marker at
55 in z.c> nil)
  compilation-next-error-function(0 nil)
  next-error-internal()
  compile-goto-error(return)
  call-interactively(compile-goto-error nil nil)

In GNU Emacs 23.0.60.1 (x86_64-unknown-freebsd7.0, GTK+ Version 2.14.7)
 of 2009-01-15 on amd64
Windowing system distributor `The X.Org Foundation', version 11.0.10402000
configured using `configure  '--prefix=/home/awn/scratch'
'--with-freetype' '--with-xft' '--enable-maintainer-mode'
'--enable-largefile' 'CC=gcc43' 'CFLAGS=-O2 -g -march=native -Wall  ''

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

Major mode: Compilation

Minor modes in effect:
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-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 input:
M-x c o m p i l e <return> C-a C-k g c c SPC - o SPC
z SPC z . c <return> C-x o M-n <return> M-x r e p o
r t - e m <tab> <return>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
(No files need saving)
Compilation finished
Mark set
pop-to-buffer: Wrong type argument: window-live-p, nil

-- 
Andrew W. Nosenko <address@hidden>



--- End Message ---
--- Begin Message --- Subject: Re: bug#1929: 23.0.60; compile-goto-error gives "pop-to-buffer: Wrong type argument: window-live-p, nil" error Date: Fri, 16 Jan 2009 17:58:29 +0100 User-agent: Thunderbird 2.0.0.16 (Windows/20080708)
Sorry, it was my fault.  I inadvertently comitted some experimental code
when reverting an earlier change.  Please try again with latest sources.

Thanks for reporting, martin.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]