From: Pierre-Luc Gauthier <p.luc.gauthier@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Custom tag exportation - Agenda export?
Date: Mon, 9 Oct 2017 14:31:40 -0400 [thread overview]
Message-ID: <CAPkan7deWFcnxVmGBfbdeFoOCyNn8R1+xnRJUTC0Tbvxr92vnw@mail.gmail.com> (raw)
Praying :
"Please let this first post of mine on this mailing list not be a duplicate…"
Hi there,
Is it possible to have agenda view templates to export a specific tag
hierarchy with all the usual org-export options (e.g.: title, toc,
LaTeX stuff, etc) ?
I have about 30 or so tags in org-tag-persistent-alist that I use in
hierarchy in most of my org file.
e.g. :
;; Errands
(:startgrouptag)
("@Errands")
(:grouptags)
("HardwareStore")
("GroceryStore")
("Bank")
(:endgrouptag)
I also have about ten+ org files registered in org-agenda-files all of
them using those tags.
All of this is working fine and as expected.
e.g.: Being able to view all subtags of @Errands in my agenda view
which resembles : "Headlines with TAGS match: @Errands"
So my question is,
How can I export this tag filtered agenda view to, say a pdf with
LaTeX customizations and all that nice stuff.
The goal would be to be able to leave the house with a beautifully
typeset document containing all @Errands tagged headers *and* content?
If I use org-agenda-write and write a PDF file, I get basically the
same screen as my view, no content, just the headers and in a rather
crude layout.
I guess what I need (conceptually) is a way to get all headers having
said tag (or being a child of) be compiled in a file. Then I know all
the cool export stuff (e.g.: HTML, LaTeX, etc) will be accessible.
I hope I was clear enough.
Thanks for your help.
--
Pierre-Luc Gauthier
next reply other threads:[~2017-10-09 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 18:31 Pierre-Luc Gauthier [this message]
2017-10-11 15:40 ` Custom tag exportation - Agenda export? Pierre-Luc Gauthier
2017-10-12 0:36 ` Matt Lundin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPkan7deWFcnxVmGBfbdeFoOCyNn8R1+xnRJUTC0Tbvxr92vnw@mail.gmail.com \
--to=p.luc.gauthier@gmail.com \
--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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.