emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Myles English <mylesenglish@gmail.com>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: Agenda printing: org-agenda-write doesn't use ps-paper-type
Date: Thu, 13 Jun 2013 21:30:49 +0100	[thread overview]
Message-ID: <87wqpxda86.fsf@gmail.com> (raw)
In-Reply-To: <87txl2jupr.fsf@sbs.ch>


Christian Egli writes:

> Myles English <mylesenglish@gmail.com> writes:
>
>> Thanks for checking it.  Yes, I had to change this line in
>> org-agenda.el:
>>
>> - (call-process "ps2pdf" nil nil nil
>> + (call-process "ps2pdf" nil nil nil "-sPAPERSIZE=a4"
>>
>> I wonder if we need to allow a set of options to be passed to ps2pdf as
>> we do for ps?
>
> Where do we pass options for ps?

Ok, options aren't passed to ps but variables can be customised for the
emacs PostScript generator:

(customize-group "ps-print")

> A quick rgrep shows that ps2pdf is used in the agenda and two of the
> exporters (groff and man) so a better option might be to set the
> papersize via the environment (GS_OPTIONS).

This worked.  I added this to my ~/.zshrc :

export GS_OPTIONS="-sPAPERSIZE=a4"

Thanks,

Myles

next prev parent reply	other threads:[~2013-06-13 20:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  1:04 Agenda printing: org-agenda-write doesn't use ps-paper-type Myles English
2013-06-12  7:31 ` Christian Egli
2013-06-12 10:06   ` Myles English
2013-06-12 16:01     ` Eric S Fraga
2013-06-12 21:57       ` Myles English
2013-06-13  7:50         ` Eric S Fraga
2013-06-13 20:39           ` Myles English
2013-06-13 21:59             ` Nick Dokos
2013-06-14  9:03             ` Eric S Fraga
2013-06-13  8:11         ` Christian Egli
2013-06-13 13:32           ` Rainer Stengele
2013-06-13 20:30           ` Myles English [this message]
2013-06-14  7:57         ` Sebastien Vauban
2013-06-14 11:41           ` Myles English
2013-06-14 11:51             ` Sebastien Vauban

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=87wqpxda86.fsf@gmail.com \
    --to=mylesenglish@gmail.com \
    --cc=christian.egli@sbs.ch \
    --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

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).