From: Daniel Clemente <n142857@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: serious calendar integration bug
Date: Thu, 28 Apr 2011 23:34:11 +0200 [thread overview]
Message-ID: <877hae6ox8.wl%n142857@gmail.com> (raw)
In-Reply-To: <BANLkTinUoKng9rjh2k6+CHN860S_JxW7jw@mail.gmail.com>
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
prev parent reply other threads:[~2011-04-28 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:06 serious calendar integration bug Matt Price
2011-04-27 19:11 ` David Maus
[not found] ` <BANLkTikyRLuEFU1C=-2KOaAZ5k_is_=gUw@mail.gmail.com>
2011-04-28 12:02 ` Matt Price
2011-04-28 12:43 ` Nick Dokos
2011-04-28 17:05 ` Matt Price
2011-04-28 21:34 ` Daniel Clemente [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hae6ox8.wl%n142857@gmail.com \
--to=n142857@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=moptop99@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).