From: Robert Goldman <rpgoldman@sift.info>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Quick aquamacs related windowing question
Date: Wed, 15 Jul 2009 10:19:15 -0500 [thread overview]
Message-ID: <4A5DF373.7020903@sift.info> (raw)
In-Reply-To: <10821.1247608443@gamaville.dokosmarshall.org>
Nick Dokos wrote:
> Robert Goldman <rpgoldman@sift.info> wrote:
>
>> I use org-mode on Aquamacs, and have some problems with the windowing.
>> E.g., when I schedule an item created with remember, aquamacs opens the
>> *Calendar* window in a different frame, then after I choose the date, I
>> am incorrectly left in that frame, instead of being returned to the
>> remember buffer. This means that my C-c C-c to save the note is
>> rejected (because it's meaningless in the *Calendar* buffer), and I have
>> to return the focus to the remember buffer by hand.
>>
>> Does anyone else see this in aquamacs? Or, if you use aquamacs and you
>> DON'T see this, would you let me know? I'd appreciate it, because it
>> would help me track down this problem...
>>
>> I suspect the problem is that (at least on aquamacs) save-excursion
>> isn't doing what I expect it to do across frames.
>>
>
> I don't know about aquamacs, but when I set calendar-setup to
> calendar-only (I usually leave it at nil which foregoes frames altogether),
> and try org-remember with C-c C-s to schedule it from the remember
> buffer, I get the calendar frame and the following error:
>
> Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
> select-window(nil)
> org-eval-in-calendar(nil t)
> byte-code(...)
> org-read-date(nil to-time nil nil nil nil)
> byte-code(...)
> org-add-planning-info(scheduled nil closed)
> org-schedule(nil)
> call-interactively(org-schedule nil nil)
>
> If I try to schedule an item in an org file, I get the frame but clicking on
> a date does not seem to do anything. So maybe org cannot deal with separate
> calendar frames.
>
Thank you very much. I only use calendar to the extent that org-mode
invokes it, so I wasn't aware of the calendar-setup variable. So I got
NIL, the same way you do.
On the other hand, on Aquamacs 1.8, based on emacs 22.3, I do not get
the error you are getting, and selecting a date works fine.
Trying to figure this out is a bit tricky, because I need to figure out
why something I expect to see is not happening, rather than something
happening wrong... I will post more as I have more results. If anyone
has any idea about what piece of code /should/ be returning the cursor
to the remember buffer, I would be grateful for any suggestions.
R
next prev parent reply other threads:[~2009-07-15 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 20:47 Quick aquamacs related windowing question Robert Goldman
2009-07-14 21:54 ` Nick Dokos
2009-07-15 15:19 ` Robert Goldman [this message]
2009-07-15 17:32 ` Robert Goldman
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=4A5DF373.7020903@sift.info \
--to=rpgoldman@sift.info \
--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).