From: Carsten Dominik <dominik@science.uva.nl>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: printing pdf of agenda buffer: two issues
Date: Fri, 6 Mar 2009 10:38:22 +0100 [thread overview]
Message-ID: <31BB812B-B0FA-4074-A5D1-2767FA94BB41@uva.nl> (raw)
In-Reply-To: <7bef1f890903052132v5f4fc87ar2f9eca6872bc9d4@mail.gmail.com>
On Mar 6, 2009, at 6:32 AM, Alan E. Davis wrote:
> Maybe I have missed something about the use of this new feature.
> And also other attempts to print have failed. So I am posing two
> questions in this post (hopefully related). They may well be due to
> my setup.
>
> 1. When I attempt to write a pdf file of a buffer of TODO items as
> collected by C-c a t, the following error is reported:
>
> comment-normalize-vars: Command attempted to use minibuffer
> while in minibuffer
> Formatting... 0%
> color-values: Wrong type argument: stringp, ("blue" :weight
> bold)
>
> There is little use in my theorizing about this.
I cannot reproduce this. C-x C-w somefile.pdf RET in my agenda works.
>
>
> 2. I have tried two other ways to print agenda output, using
> scripts posted elsewhere. One of them was a script from an org-mode
> tutorial, and the other, perhaps, from the FAQ. Both times, I get
> colored text that cannot print. It is pale yellow.
Very likel this is because you are using a script that
runs Emacs in batch-mode, in which case the font colors
are poorly defined. You can try to bind org-agenda-with-colors
to nil during the agenda command, as one of the options.
>
>
> Perhaps these are related?
I don't think so.
HTH
- Carsten
next prev parent reply other threads:[~2009-03-06 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 5:32 printing pdf of agenda buffer: two issues Alan E. Davis
2009-03-06 9:38 ` Carsten Dominik [this message]
2009-03-13 13:01 ` Ivan Nedrehagen
2009-03-13 17:10 ` Carsten Dominik
2009-03-16 8:12 ` Ivan Nedrehagen
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=31BB812B-B0FA-4074-A5D1-2767FA94BB41@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=lngndvs@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).