From: Robert Goldman <rpgoldman@sift.info>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: More problems with Mobile Org agenda writing
Date: Thu, 29 Jul 2010 17:45:18 -0500 [thread overview]
Message-ID: <4C52047E.1040809@sift.info> (raw)
In-Reply-To: <4C518DA3.4000908@sift.info>
On 7/29/10 Jul 29 -9:18 AM, Robert Goldman wrote:
> I posted an email yesterday about a problem I was having writing agendas
> for MobileOrg, where org-mode seemed to think it should be writing my
> agendas as postscript.
>
> I thought perhaps this was a problem with the old version of Aquamacs
> that I have been using, so I finally got myself to upgrade to Aquamacs
> 2.0 (Emacs 23.2).
>
> Now I get a /different/ error, but it's still an error where org-mode
> seems to believe the agenda should be written as postscript. I can't
> see why this should be happening. Here's the backtrace:
I was discussing this with a colleague of mine, and he had a hypothesis
that might be correct.
The code in org-write-agenda looks like it has been rewritten to make
FLET be expanded at compile time, so it needn't be present at run-time.
However, I wonder if this was done properly, or whether the backquote
expansion is causing the /body/ of the flet to be evaluated at run-time
(instead of having it be macroexpanded once at compile time).
This would account for the symptoms I'm seeing: I tried putting a DEBUG
statement before the call to ps-print-buffer-with-faces, and that debug
statement was never executed, further, when I examine the value of the
FILE local variable in the debugger, it clearly isn't a value that would
trigger a call to ps-print-buffer-with-faces.
I believe what's wanted here is macroexpansion and not evaluation, yes?
More as I discover more,
R
prev parent reply other threads:[~2010-07-29 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 14:18 More problems with Mobile Org agenda writing Robert Goldman
2010-07-29 22:45 ` Robert Goldman [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=4C52047E.1040809@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
/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).