emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Manish <mailtomanish.sharma@gmail.com>
Cc: James <jamesodhunt@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [Buglet] issue where org-agenda always prints to PostScript "with faces"
Date: Thu, 18 Jun 2009 09:57:08 +0200	[thread overview]
Message-ID: <19F2922D-780A-4431-AA01-56CE37EFEB8B@gmail.com> (raw)
In-Reply-To: <e7cdbe30906160827v18ec9c2co68daa0c491b97cab@mail.gmail.com>


On Jun 16, 2009, at 5:27 PM, Manish wrote:

>  On Tue, Jun 16, 2009 at 9:49 AM, James wrote:
>> If you tweak org-agenda-custom-commands to create a PostScript  
>> version
>> of your agenda (for example by following this link...
>>
>> http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.php#sec-5.4
>>
>> ) ... and like me you happen to use a dark background in Emacs
>> (set-face-background 'default "black"), you end up with PostScript
>> files which take account of your background colour. In my case if I
>> were to actually print my agenda on a printer, I'd probably drain it
>> of black ink! :-)
>>
>> This problem appears to be because org-agenda always prints using
>> "ps-print-buffer-with-faces".
>>
>> Please could a variable be added such that for awkward users like me
>> org-mode would use "ps-print-buffer" instead.
>
> A similar issue was dicussed in this thread
> http://thread.gmane.org/gmane.emacs.orgmode/12719

I the mean time, I have found a better solution for this.

(setq org-agenda-exporter-settings
       '((ps-print-color-p 'black-white)))


Matt, or anyone, maybe this is worth a FAQ entry?

- Carsten

  reply	other threads:[~2009-06-18  8:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  4:19 [Buglet] issue where org-agenda always prints to PostScript "with faces" James
2009-06-16 15:27 ` Manish
2009-06-18  7:57   ` Carsten Dominik [this message]
2009-06-18 16:56     ` Manish

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=19F2922D-780A-4431-AA01-56CE37EFEB8B@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jamesodhunt@gmail.com \
    --cc=mailtomanish.sharma@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).