El Thu, 28 Apr 2011 08:02:33 -0400 Matt Price va escriure: > > debug(error (wrong-type-argument window-live-p nil)) > select-window(nil) > org-eval-in-calendar(nil t) >
I often experience a similar bug but with frames instead of windows: ;Debugger entered--Lisp error: (wrong-type-argument frame-live-p #<dead frame *Minibuf-1* 0xcf00da0>) ; frame-selected-window(#<dead frame *Minibuf-1* 0xcf00da0>) ; menu-bar-non-minibuffer-window-p() ; kill-this-buffer() ; call-interactively(kill-this-buffer nil nil) My solution when this happpens is: (setq menu-updating-frame nil) I use this for many years and it always restores Emacs and I call close buffers again. Maybe it works for you. I think I might also have experienced your bug: after opening another buffer from Org and messing around, my .org file was completely empty and C-x C-s would save all contents to disk. I think it was either due to vc (C-x v =) or due to the calendar when scheduling a task. Try changing focus some times: from .org to the calendar, back, etc. This happened about 3 or 4 weeks ago, but several times. I updated and recompiled Emacs and org and now it doesn't seem to happen. I don't have detailed information, sorry (I thought it was so severe that many people would notice it). My workaround: use a version control system, and execute regularly „[VCS] diff > /tmp/backup1“. And fear Emacs. -- Daniel
