From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Myles English <mylesenglish@gmail.com>
Cc: emacs-orgmode@gnu.org, Christian Egli <christian.egli@sbs.ch>
Subject: Re: Agenda printing: org-agenda-write doesn't use ps-paper-type
Date: Fri, 14 Jun 2013 10:03:40 +0100 [thread overview]
Message-ID: <87k3lxqh7o.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87vc5hd9uc.fsf@gmail.com> (Myles English's message of "Thu, 13 Jun 2013 21:39:07 +0100")
Myles English <mylesenglish@gmail.com> writes:
> Eric,
>
> Eric S Fraga writes:
>> If you use a4 sized paper all (or most of) the time, you can set this in
>> /etc/papersize on Linux. I think this is what ps2pdf looks at by
>> default.
>>
> Thanks for the suggestions. I looked into this for my Arch Linux but it
> had no effect on ps2pdf. Making the /etc/papersize file and then
> setting PAPERSIZE=a4 or PAPERCONF=/etc/papersize did not produce an A4
> pdf document (even after installing libpaper).
On my Debian system, the file /etc/papersize has simply "a4" as the
contents. No "PAPERSIZE" or similar. According to the manual page for
papersize in section 5, this file is used unless overridden by the
environment variables PAPERSIZE or PAPERCONF, the latter pointing to a
file which specifies the size.
YMMV, of course.
Anyway, glad you sorted out your problem!
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.3-193-g334581
next prev parent reply other threads:[~2013-06-14 9:04 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 [this message]
2013-06-13 8:11 ` Christian Egli
2013-06-13 13:32 ` Rainer Stengele
2013-06-13 20:30 ` Myles English
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=87k3lxqh7o.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
--cc=mylesenglish@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).