emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastien.guerry@wikimedia.fr>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Kyle Farrell <kaf@nwlink.com>, emacs-orgmode@gnu.org
Subject: Re: export weekly completed/late items
Date: Wed, 09 Feb 2011 17:52:36 +0100	[thread overview]
Message-ID: <87oc6li20b.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTinJ9n_wBxemNM3tCiaQkEMFhsaVkuOc23kTJQn_@mail.gmail.com> (Marcelo de Moraes Serpa's message of "Wed, 9 Feb 2011 10:41:35 -0600")

Hi Marcelo,

Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:

> Although I have been using org for quite some time, I never really
> spend time going through the manual and learning all the nuances of
> the agenda, and I often forget how powerful it is.

It's a good read :)

> It would really nice if we had an agenda command to export all of this
> as a PDF report, for example.

You can export agendas as PDF by writing them to .pdf files.

See section 10.5 in the manual: "Commands in the agenda buffer"

`C-x C-w     (`org-write-agenda')'
     Write the agenda view to a file.  Depending on the extension of
     the selected file name, the view will be exported as HTML
     (extension `.html' or `.htm'), Postscript (extension `.ps'), PDF
     (extension `.pdf'), and plain text (any other extension).  When
     called with a `C-u' prefix argument, immediately open the newly
     created file.  Use the variable `org-agenda-exporter-settings' to
     set options for `ps-print' and for `htmlize' to be used during
     export.

HTH,

-- 
 Bastien

      reply	other threads:[~2011-02-09 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 20:04 export weekly completed/late items Kyle Farrell
2011-02-08 18:14 ` Marcelo de Moraes Serpa
2011-02-08 19:30   ` Kyle Farrell
2011-02-09 15:36     ` Christopher Allan Webber
2011-02-09 16:41       ` Marcelo de Moraes Serpa
2011-02-09 16:52         ` Bastien [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=87oc6li20b.fsf@gnu.org \
    --to=bastien.guerry@wikimedia.fr \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaf@nwlink.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).