Re: [O] Org-Publish of a PDF ??
Richard Lawrence writes: > David Masterson writes: >> When I publish my project, I find that my org files are first generated >> into tex and pdf files in directory1 and then the tex/pdf files are >> copied to directory2. What I would like is for the tex/pdf files to be >> directly generated in directory2 with no "extras" in directory1. > I think you might be thinking about this the wrong way around. I may be > wrong about this, as I'm not a heavy user of the publishing framework, > but here's my two cents. > > As far as I understand it, the publishing framework is basically > designed around the idea of copying finished products to a desired > location (a directory, either locally or on a webserver). It's built as > a layer on top of Org's exporters, not as a way to make those exporters > behave differently. If you want to control the *build* process for the > PDF, as opposed to just where it finally ends up, you probably want to > set options for the latex exporter, not the publishing framework. > > In particular, you might want something like: > > #+EXPORT_FILE_NAME: builddir/file.tex > > in the Org files you're exporting, where builddir is somewhere outside > of your directory1. (I'm *pretty* sure that will work, but I haven't > tested it.) Hmm. That's a possibility. Then, I assume, that, after EXPORT_FILE_NAME is made, the PDF file will be made in the same location. I'll have a look at the exporter options more. I wonder if there is an EXPORT_DIR..? -- David
Re: [O] Org-Publish of a PDF ??
Hi David, David Masterson writes: > When I publish my project, I find that my org files are first generated > into tex and pdf files in directory1 and then the tex/pdf files are > copied to directory2. What I would like is for the tex/pdf files to be > directly generated in directory2 with no "extras" in directory1. I think you might be thinking about this the wrong way around. I may be wrong about this, as I'm not a heavy user of the publishing framework, but here's my two cents. As far as I understand it, the publishing framework is basically designed around the idea of copying finished products to a desired location (a directory, either locally or on a webserver). It's built as a layer on top of Org's exporters, not as a way to make those exporters behave differently. If you want to control the *build* process for the PDF, as opposed to just where it finally ends up, you probably want to set options for the latex exporter, not the publishing framework. In particular, you might want something like: #+EXPORT_FILE_NAME: builddir/file.tex in the Org files you're exporting, where builddir is somewhere outside of your directory1. (I'm *pretty* sure that will work, but I haven't tested it.) Hope that helps! -- Best, Richard
Re: [O] org-publish: docview all pdf files
Hi Vikas, maybe you could make me a minimal setup so that I can reproduce this? Just a little folder with two files and a minimal .emacs that defines publishing of these files to some other directory. That would be useful. - Carsten On 7.6.2013, at 18:15, Vikas Rawal vikasli...@agrarianresearch.org wrote: When I publish the project, orgmode attempts to open all pdf files (which are static content). It seems to me that some sort of indexing is being attempted though I am not sure. I think it started happening after I included creation of a sitemap. I get messages like this: DocView: process pdf/ps-png changed status to killed. This slows down publishing considerably. I have just added some large pdf files, and now it asks me for each such file whether I want to open it. org-publish gets stuck if I say yes, and aborts publishing if I say no. Is there a way, I could tell orgmode to not try to process these pdf files. pdf files are being processed through a sub-project that deals with static content (org-publish-attachment). Would be grateful for any advice. Best, Vikas signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] org Publish subtree to pdf
Thanks for your answers. That worked perfectly. Martin From: n.goaz...@gmail.com To: mart...@hotmail.com CC: emacs-orgmode@gnu.org Subject: Re: org Publish subtree to pdf Date: Sat, 17 Aug 2013 10:28:06 +0200 Hello, Martin Leduc mart...@hotmail.com writes: I have a large org file with several projects in it. I can export one of them (a subtree) to pdf by using C-c C-e C-s l o. However, I would like to use the Publish function since it allows to export the pdf to another folder. However, by using C-s (Subtree option) and P (for publish) and x (to choose template from org-publish-project-alist), the Subtree option does not seem to work well. Subtree export is not meant to be used along with publishing. The latter works on complete files only. The entire tree is exported though without the content of higher-level headlines. Is it the normal behavior to be expected from the publish function ? What is the best way to export in pdf to another location ? Use EXPORT_FILE_NAME node property. See penultimate paragraph from section 12.3 in the manual. Regards, -- Nicolas Goaziou
Re: [O] org Publish subtree to pdf
Hi Martin, On Sat, Aug 17, 2013 at 01:58:57AM +, Martin Leduc wrote: Is it the normal behavior to be expected from the publish function ? There is some setup required to use publish. (info (org) Publishing) What is the best way to export in pdf to another location ? You can simply set the :EXPORT_FILE_NAME: property with a filename in a subdirectory. Something like: * subtree to export :PROPERTIES: :EXPORT_FILE_NAME: subdir/exported.pdf :END: Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] org Publish subtree to pdf
Hello, Martin Leduc mart...@hotmail.com writes: I have a large org file with several projects in it. I can export one of them (a subtree) to pdf by using C-c C-e C-s l o. However, I would like to use the Publish function since it allows to export the pdf to another folder. However, by using C-s (Subtree option) and P (for publish) and x (to choose template from org-publish-project-alist), the Subtree option does not seem to work well. Subtree export is not meant to be used along with publishing. The latter works on complete files only. The entire tree is exported though without the content of higher-level headlines. Is it the normal behavior to be expected from the publish function ? What is the best way to export in pdf to another location ? Use EXPORT_FILE_NAME node property. See penultimate paragraph from section 12.3 in the manual. Regards, -- Nicolas Goaziou
