'thinking out loud here: Maybe I could make a errandsExport.org file in whish I could include all my agenda files and then filter only the Errands tag. Then I could add all the LaTeX options I want for this export file e.g. #+TITLE: My errands document
I do have problems including all org-agenda-files files. I tried : #+INCLUDE: (org-agenda-files) which obviously does not work but I do not know how to tackle this (I'm guessing) rather simple issue. How could I expand this org-agenda-files variable for org to include it's content? Is this an OK way to go about it? Also, I have not found a way to filter tags out of an org file at export. I know about #+SELECT_TAGS: and #+EXCLUDE_TAGS: but what if you *only* want trees with the "Errands" tag? Is there a way to exclude all and then select a specific tag? Thanks for any pointers :-) -- Pierre-Luc Gauthier 2017-10-09 14:31 GMT-04:00 Pierre-Luc Gauthier <p.luc.gauth...@gmail.com>: > 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) ? > > 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.
