From: Matt Price <moptop99@gmail.com>
To: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: serious calendar integration bug
Date: Thu, 28 Apr 2011 13:05:26 -0400 [thread overview]
Message-ID: <BANLkTi=X1TRCG8LGqOOQ-2SD7tdvQOpABQ@mail.gmail.com> (raw)
In-Reply-To: <10947.1303994607@alphaville.dokosmarshall.org>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
On Thu, Apr 28, 2011 at 8:43 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> Matt Price <moptop99@gmail.com> wrote:
>
>
> One thing is to make sure that it is the first select-window which is
> failing:
> there is a second one in there as well. Toggling debug-on-error and getting
> a full backtrace (assuming you are loading .el files and not .elc files)
> would
> take care of that.
>
> If there were any concurrency, I'd suspect a race: you try to select a
> window
> that somebody else killed in the meantime. But I don't think there is
> anything
> like that going in emacs - but I don't know for sure.
>
I think I'm loading .el files, from the git repository. And I think it must
be the first select-window failing, because (get-buffer-window
"*Calendar*") evaluates to nil, while (selected-window) evaluates to a
numbered window. "*scratch*" also works properly, so there's so mething
very odd about the *Calendar* window. There must be something strange
happening with the calendar functions -- that's part of the emacs core,
right? Or should I be worrying about my other packages?
Again, many thanks,
Matt
> Nick
>
[-- Attachment #2: Type: text/html, Size: 1737 bytes --]
next prev parent reply other threads:[~2011-04-28 17:05 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 [this message]
2011-04-28 21:34 ` Daniel Clemente
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='BANLkTi=X1TRCG8LGqOOQ-2SD7tdvQOpABQ@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).