Re: [Orgmode] One org file, multiple exports, is it possible?
Aloha Carsten, Thanks for looking into this. I'm trying to document the different ways to export part of an org file to LaTeX in the hope of augmenting the tutorial on Worg. I thought I understood the tag selection logic, so the results I got puzzled me. Now that I know the expected behavior, I'll look more closely to see why I'm not getting it. Hopefully, I'll be able to puzzle it through myself and won't have to pester you and the list with my idea of a minimal .emacs, etc. I appreciate your offer to take another look if I'm not successful. All the best, Tom On May 23, 2010, at 7:20 PM, Carsten Dominik wrote: On May 24, 2010, at 12:01 AM, Thomas S. Dye wrote: Thanks Carsten, That was it. It works with just the select tags here, too. One more query. I get different export results depending on where I specify the select tag. Given the following org-mode file, specifying the select tag in the file header with # +EXPORT_SELECT_TAGS: @WORK exports only the tree tagged with @WORK, but specifying the select tag in the publishing setup with :select- tags (@WORK), and without any specification in the file header, exports two trees, the first untagged tree and the tree tagged with @WORK. Is this the expected behavior? Of course not. And I cannot reproduce it either. Maybe you need to make me an exact test case, with minimal .emacs, and both testcase files. Make it as a zip archive, so that I am sure I have the same amount of whitespace at the beginning of the files etc. Thanks. - Carsten -- org file - * Untagged notes before tags Where do these go? * Work notes :@WORK: This should end up somewhere. * Home notes :@HOME: This should end up somewhere else. -- org file - All the best, Tom On May 23, 2010, at 10:57 AM, Carsten Dominik wrote: On May 23, 2010, at 8:49 PM, Thomas S. Dye wrote: Aloha all, Karl's setup specified keyword arguments for :select-tags but not for :exclude-tags. When I tried this setup with only :select- tags it worked as expected for the select tag that occurs first in the Org-mode file, but the publishing project defined for the select tag that occurs second in the Org-mode file did not work as expected. In this case, trees with both select tags appear in the output file. I solved my problem by also specifying exclude tags. Here is the setup that worked for me. .emacs fragment -- (add-to-list 'org-publish-project-alist '(work :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-work/ :publishing-function org-publish-org-to-latex :select-tags (@WORK) :exclude-tags (@HOME) :title Work Notes :include (index.org) :exclude \\.org$ )) (add-to-list 'org-publish-project-alist '(home :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-home/ :publishing-function org-publish-org-to-latex :select-tags (@HOME) :exclude-tags (@WORK) :title Home Phone :include (index.org) :exclude \\.org$ )) .emacs fragment -- org-mode file -- * Work notes :@WORK: This should end up in publish-work. * Home notes :@HOME: This should end up in publish-home. org-mode file -- I'm wondering, is it really possible to get the expected results specifying only select tags and not exclude tags? Works perfectly fine for me! Note that changing the publishing alist does not trigger republishing. Use C-u with the publishing command... - Carsten All the best, Tom On May 23, 2010, at 6:31 AM, Karl Martino wrote: Hi, Ah! This worked once I tried this tip Carsten - thanks! I should have realized that the buffer setting was defeating that there. You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. Eric, thanks for the tip as well. I will check out org-jekyll even though this worked because producing a blog or some kind of knowledge base from my single-org-mode-life-file sounds great :) Thanks, Karl On Sun, May 23, 2010 at 12:17 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On May 23, 2010, at 2:22 PM, Karl Martino wrote: Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. No, it does in fact work, I just tested it. Here is the setup I used: (setq org-publish-project-alist '((ttt
Re: [Orgmode] One org file, multiple exports, is it possible?
Aloha Carsten, I think I need to know what is meant by minimal .emacs. I've poked around quite a bit now and have discovered two things: 1) Two lines in Karl's org-publish-project-alist triggered the unexpected behavior. These are the lines with the :include and :exclude keywords. 2) The unexpected behavior only occurs when org-publish-project-alist also contains a project of the form (project-name :components (project-name project-name ...)). Here, I've only checked the situation where the offending project involves sub-projects that are not Karl's. I have two reservations about putting together a minimal .emacs: 1) I'm using Eric Schulte's literate emacs starter kit, so my initialization files are split up into many parts, only two of which I fiddle with. I'm happily ignorant of what goes on before my two org configuration files get processed by Eric's code. 2) The org-publish-project-alist variable in my configuration contains paths that are (probably) unique to my system. That said, if a minimal .emacs is required, please give me some direction and I'll do what I can. All the best, Tom On May 23, 2010, at 7:20 PM, Carsten Dominik wrote: On May 24, 2010, at 12:01 AM, Thomas S. Dye wrote: Thanks Carsten, That was it. It works with just the select tags here, too. One more query. I get different export results depending on where I specify the select tag. Given the following org-mode file, specifying the select tag in the file header with # +EXPORT_SELECT_TAGS: @WORK exports only the tree tagged with @WORK, but specifying the select tag in the publishing setup with :select- tags (@WORK), and without any specification in the file header, exports two trees, the first untagged tree and the tree tagged with @WORK. Is this the expected behavior? Of course not. And I cannot reproduce it either. Maybe you need to make me an exact test case, with minimal .emacs, and both testcase files. Make it as a zip archive, so that I am sure I have the same amount of whitespace at the beginning of the files etc. Thanks. - Carsten -- org file - * Untagged notes before tags Where do these go? * Work notes :@WORK: This should end up somewhere. * Home notes :@HOME: This should end up somewhere else. -- org file - All the best, Tom On May 23, 2010, at 10:57 AM, Carsten Dominik wrote: On May 23, 2010, at 8:49 PM, Thomas S. Dye wrote: Aloha all, Karl's setup specified keyword arguments for :select-tags but not for :exclude-tags. When I tried this setup with only :select- tags it worked as expected for the select tag that occurs first in the Org-mode file, but the publishing project defined for the select tag that occurs second in the Org-mode file did not work as expected. In this case, trees with both select tags appear in the output file. I solved my problem by also specifying exclude tags. Here is the setup that worked for me. .emacs fragment -- (add-to-list 'org-publish-project-alist '(work :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-work/ :publishing-function org-publish-org-to-latex :select-tags (@WORK) :exclude-tags (@HOME) :title Work Notes :include (index.org) :exclude \\.org$ )) (add-to-list 'org-publish-project-alist '(home :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-home/ :publishing-function org-publish-org-to-latex :select-tags (@HOME) :exclude-tags (@WORK) :title Home Phone :include (index.org) :exclude \\.org$ )) .emacs fragment -- org-mode file -- * Work notes :@WORK: This should end up in publish-work. * Home notes :@HOME: This should end up in publish-home. org-mode file -- I'm wondering, is it really possible to get the expected results specifying only select tags and not exclude tags? Works perfectly fine for me! Note that changing the publishing alist does not trigger republishing. Use C-u with the publishing command... - Carsten All the best, Tom On May 23, 2010, at 6:31 AM, Karl Martino wrote: Hi, Ah! This worked once I tried this tip Carsten - thanks! I should have realized that the buffer setting was defeating that there. You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. Eric, thanks
Re: [Orgmode] One org file, multiple exports, is it possible?
Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. The issue with #+TITLE in the buffer is that it is the same file I am exporting various times, just with different tag filters, and the title then remains the same for each export, where I want it to reflect the subset of the file, ie Karl's Work Journal, or Karl's Home Journal. A workaround that just occurred to me: I could write a method that would change the #+TITLE value in the buffer, then org-reload, before exporting the component in the list. That should work. But am I missing something? Thanks again, org-mode is fantastic and has helped me wrangle a lot of complexity into something portable and easy to use. It's been a lifesaver for me :) Thanks, Karl (setq org-publish-project-alist '( (highlights :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export :publishing-function org-publish-org-to-html :select-tags (highlight) :include (index.org) I have not tried it, but if you do not have #+TITLE in the buffer, then :title This is my title in the publishing plist might work. Give it a try. - Carsten ) (work :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/work/ :publishing-function org-publish-org-to-html :select-tags (@WORK) :include (index.org) :exclude \\.org$ ) (home :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/home/ :publishing-function org-publish-org-to-html :select-tags (@HOME) :include (index.org) :exclude \\.org$ :link-up ) )) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] One org file, multiple exports, is it possible?
Hi Karl, Maybe the following little function will work. If called from an org-mode file, it will try to export each subtree, respecting the values of EXPORT_FILE_NAME and EXPORT_TITLE. --8---cut here---start-8--- (defun org-export-parts () (interactive) (org-map-entries (lambda () (outline-mark-subtree) (org-export-as-html nil --8---cut here---end---8--- it shouldn't be difficult to augment the above to set exporting options based on the values of subtree tags. If this isn't sufficient, and you want really powerful templating of different classes of html files you could try out jekyll [1], and some of the org-jekyll solutions [2]. Hope this helps -- Eric Footnotes: [1] http://jekyllrb.com/ [2] http://orgmode.org/worg/org-tutorials/org-jekyll.php ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] One org file, multiple exports, is it possible?
On May 23, 2010, at 2:22 PM, Karl Martino wrote: Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. No, it does in fact work, I just tested it. Here is the setup I used: (setq org-publish-project-alist '((ttt :base-directory ~/lib/emacs/work/org-mode/t/pub/src :base-extension org :publishing-directory ~/lib/emacs/work/org-mode/t/pub/target :section-numbers nil :table-of-contents nil ;; :plain-source t ;; :htmlized-source t :exclude -source :title Test :title property :auto-sitemap t :makeindex t :publishing-function (org-publish-org-to-html org-publish-org-to- org You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. - Carsten The issue with #+TITLE in the buffer is that it is the same file I am exporting various times, just with different tag filters, and the title then remains the same for each export, where I want it to reflect the subset of the file, ie Karl's Work Journal, or Karl's Home Journal. A workaround that just occurred to me: I could write a method that would change the #+TITLE value in the buffer, then org-reload, before exporting the component in the list. That should work. But am I missing something? Thanks again, org-mode is fantastic and has helped me wrangle a lot of complexity into something portable and easy to use. It's been a lifesaver for me :) Thanks, Karl (setq org-publish-project-alist '( (highlights :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export :publishing-function org-publish-org-to-html :select-tags (highlight) :include (index.org) I have not tried it, but if you do not have #+TITLE in the buffer, then :title This is my title in the publishing plist might work. Give it a try. - Carsten ) (work :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/work/ :publishing-function org-publish-org-to-html :select-tags (@WORK) :include (index.org) :exclude \\.org$ ) (home :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/home/ :publishing-function org-publish-org-to-html :select-tags (@HOME) :include (index.org) :exclude \\.org$ :link-up ) )) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] One org file, multiple exports, is it possible?
Hi, Ah! This worked once I tried this tip Carsten - thanks! I should have realized that the buffer setting was defeating that there. You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. Eric, thanks for the tip as well. I will check out org-jekyll even though this worked because producing a blog or some kind of knowledge base from my single-org-mode-life-file sounds great :) Thanks, Karl On Sun, May 23, 2010 at 12:17 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On May 23, 2010, at 2:22 PM, Karl Martino wrote: Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. No, it does in fact work, I just tested it. Here is the setup I used: (setq org-publish-project-alist '((ttt :base-directory ~/lib/emacs/work/org-mode/t/pub/src :base-extension org :publishing-directory ~/lib/emacs/work/org-mode/t/pub/target :section-numbers nil :table-of-contents nil ;; :plain-source t ;; :htmlized-source t :exclude -source :title Test :title property :auto-sitemap t :makeindex t :publishing-function (org-publish-org-to-html org-publish-org-to-org You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. - Carsten The issue with #+TITLE in the buffer is that it is the same file I am exporting various times, just with different tag filters, and the title then remains the same for each export, where I want it to reflect the subset of the file, ie Karl's Work Journal, or Karl's Home Journal. A workaround that just occurred to me: I could write a method that would change the #+TITLE value in the buffer, then org-reload, before exporting the component in the list. That should work. But am I missing something? Thanks again, org-mode is fantastic and has helped me wrangle a lot of complexity into something portable and easy to use. It's been a lifesaver for me :) Thanks, Karl (setq org-publish-project-alist '( (highlights :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export :publishing-function org-publish-org-to-html :select-tags (highlight) :include (index.org) I have not tried it, but if you do not have #+TITLE in the buffer, then :title This is my title in the publishing plist might work. Give it a try. - Carsten ) (work :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/work/ :publishing-function org-publish-org-to-html :select-tags (@WORK) :include (index.org) :exclude \\.org$ ) (home :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/home/ :publishing-function org-publish-org-to-html :select-tags (@HOME) :include (index.org) :exclude \\.org$ :link-up ) )) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten -- Seek First to Understand, Then to be Understood” - Steven Covey www.paradox1x.org, www.phillyfuture.org, @kmartino ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] One org file, multiple exports, is it possible?
Aloha all, Karl's setup specified keyword arguments for :select-tags but not for :exclude-tags. When I tried this setup with only :select-tags it worked as expected for the select tag that occurs first in the Org- mode file, but the publishing project defined for the select tag that occurs second in the Org-mode file did not work as expected. In this case, trees with both select tags appear in the output file. I solved my problem by also specifying exclude tags. Here is the setup that worked for me. .emacs fragment -- (add-to-list 'org-publish-project-alist '(work :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-work/ :publishing-function org-publish-org-to-latex :select-tags (@WORK) :exclude-tags (@HOME) :title Work Notes :include (index.org) :exclude \\.org$ )) (add-to-list 'org-publish-project-alist '(home :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-home/ :publishing-function org-publish-org-to-latex :select-tags (@HOME) :exclude-tags (@WORK) :title Home Phone :include (index.org) :exclude \\.org$ )) .emacs fragment -- org-mode file -- * Work notes :@WORK: This should end up in publish-work. * Home notes :@HOME: This should end up in publish-home. org-mode file -- I'm wondering, is it really possible to get the expected results specifying only select tags and not exclude tags? All the best, Tom On May 23, 2010, at 6:31 AM, Karl Martino wrote: Hi, Ah! This worked once I tried this tip Carsten - thanks! I should have realized that the buffer setting was defeating that there. You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. Eric, thanks for the tip as well. I will check out org-jekyll even though this worked because producing a blog or some kind of knowledge base from my single-org-mode-life-file sounds great :) Thanks, Karl On Sun, May 23, 2010 at 12:17 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On May 23, 2010, at 2:22 PM, Karl Martino wrote: Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. No, it does in fact work, I just tested it. Here is the setup I used: (setq org-publish-project-alist '((ttt :base-directory ~/lib/emacs/work/org-mode/t/pub/src :base-extension org :publishing-directory ~/lib/emacs/work/org-mode/t/pub/ target :section-numbers nil :table-of-contents nil ;; :plain-source t ;; :htmlized-source t :exclude -source :title Test :title property :auto-sitemap t :makeindex t :publishing-function (org-publish-org-to-html org-publish-org-to-org You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. - Carsten The issue with #+TITLE in the buffer is that it is the same file I am exporting various times, just with different tag filters, and the title then remains the same for each export, where I want it to reflect the subset of the file, ie Karl's Work Journal, or Karl's Home Journal. A workaround that just occurred to me: I could write a method that would change the #+TITLE value in the buffer, then org-reload, before exporting the component in the list. That should work. But am I missing something? Thanks again, org-mode is fantastic and has helped me wrangle a lot of complexity into something portable and easy to use. It's been a lifesaver for me :) Thanks, Karl (setq org-publish-project-alist '( (highlights :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export :publishing-function org-publish-org-to-html :select-tags (highlight) :include (index.org) I have not tried it, but if you do not have #+TITLE in the buffer, then :title This is my title in the publishing plist might work. Give it a try. - Carsten ) (work :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/work/ :publishing-function org-publish-org-to-html :select-tags (@WORK) :include (index.org) :exclude \\.org$ ) (home :base-directory ~/notes/org/ :base-extension org :publishing-directory
Re: [Orgmode] One org file, multiple exports, is it possible?
On May 23, 2010, at 8:49 PM, Thomas S. Dye wrote: Aloha all, Karl's setup specified keyword arguments for :select-tags but not for :exclude-tags. When I tried this setup with only :select-tags it worked as expected for the select tag that occurs first in the Org-mode file, but the publishing project defined for the select tag that occurs second in the Org-mode file did not work as expected. In this case, trees with both select tags appear in the output file. I solved my problem by also specifying exclude tags. Here is the setup that worked for me. .emacs fragment -- (add-to-list 'org-publish-project-alist '(work :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-work/ :publishing-function org-publish-org-to-latex :select-tags (@WORK) :exclude-tags (@HOME) :title Work Notes :include (index.org) :exclude \\.org$ )) (add-to-list 'org-publish-project-alist '(home :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-home/ :publishing-function org-publish-org-to-latex :select-tags (@HOME) :exclude-tags (@WORK) :title Home Phone :include (index.org) :exclude \\.org$ )) .emacs fragment -- org-mode file -- * Work notes :@WORK: This should end up in publish-work. * Home notes :@HOME: This should end up in publish-home. org-mode file -- I'm wondering, is it really possible to get the expected results specifying only select tags and not exclude tags? Works perfectly fine for me! Note that changing the publishing alist does not trigger republishing. Use C-u with the publishing command... - Carsten All the best, Tom On May 23, 2010, at 6:31 AM, Karl Martino wrote: Hi, Ah! This worked once I tried this tip Carsten - thanks! I should have realized that the buffer setting was defeating that there. You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. Eric, thanks for the tip as well. I will check out org-jekyll even though this worked because producing a blog or some kind of knowledge base from my single-org-mode-life-file sounds great :) Thanks, Karl On Sun, May 23, 2010 at 12:17 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On May 23, 2010, at 2:22 PM, Karl Martino wrote: Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. No, it does in fact work, I just tested it. Here is the setup I used: (setq org-publish-project-alist '((ttt :base-directory ~/lib/emacs/work/org-mode/t/pub/src :base-extension org :publishing-directory ~/lib/emacs/work/org-mode/t/pub/ target :section-numbers nil :table-of-contents nil ;; :plain-source t ;; :htmlized-source t :exclude -source :title Test :title property :auto-sitemap t :makeindex t :publishing-function (org-publish-org-to-html org-publish-org-to-org You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. - Carsten The issue with #+TITLE in the buffer is that it is the same file I am exporting various times, just with different tag filters, and the title then remains the same for each export, where I want it to reflect the subset of the file, ie Karl's Work Journal, or Karl's Home Journal. A workaround that just occurred to me: I could write a method that would change the #+TITLE value in the buffer, then org-reload, before exporting the component in the list. That should work. But am I missing something? Thanks again, org-mode is fantastic and has helped me wrangle a lot of complexity into something portable and easy to use. It's been a lifesaver for me :) Thanks, Karl (setq org-publish-project-alist '( (highlights :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export :publishing-function org-publish-org-to-html :select-tags (highlight) :include (index.org) I have not tried it, but if you do not have #+TITLE in the buffer, then :title This is my title in the publishing plist might work. Give it a try. - Carsten ) (work :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/work/ :publishing-function org-publish-org-to-html :select-tags (@WORK)
Re: [Orgmode] One org file, multiple exports, is it possible?
Thanks Carsten, That was it. It works with just the select tags here, too. One more query. I get different export results depending on where I specify the select tag. Given the following org-mode file, specifying the select tag in the file header with #+EXPORT_SELECT_TAGS: @WORK exports only the tree tagged with @WORK, but specifying the select tag in the publishing setup with :select-tags (@WORK), and without any specification in the file header, exports two trees, the first untagged tree and the tree tagged with @WORK. Is this the expected behavior? -- org file - * Untagged notes before tags Where do these go? * Work notes :@WORK: This should end up somewhere. * Home notes :@HOME: This should end up somewhere else. -- org file - All the best, Tom On May 23, 2010, at 10:57 AM, Carsten Dominik wrote: On May 23, 2010, at 8:49 PM, Thomas S. Dye wrote: Aloha all, Karl's setup specified keyword arguments for :select-tags but not for :exclude-tags. When I tried this setup with only :select-tags it worked as expected for the select tag that occurs first in the Org-mode file, but the publishing project defined for the select tag that occurs second in the Org-mode file did not work as expected. In this case, trees with both select tags appear in the output file. I solved my problem by also specifying exclude tags. Here is the setup that worked for me. .emacs fragment -- (add-to-list 'org-publish-project-alist '(work :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-work/ :publishing-function org-publish-org-to-latex :select-tags (@WORK) :exclude-tags (@HOME) :title Work Notes :include (index.org) :exclude \\.org$ )) (add-to-list 'org-publish-project-alist '(home :base-directory ~/org/temp/ :base-extension org :publishing-directory ~/org/temp/publish-home/ :publishing-function org-publish-org-to-latex :select-tags (@HOME) :exclude-tags (@WORK) :title Home Phone :include (index.org) :exclude \\.org$ )) .emacs fragment -- org-mode file -- * Work notes :@WORK: This should end up in publish-work. * Home notes :@HOME: This should end up in publish-home. org-mode file -- I'm wondering, is it really possible to get the expected results specifying only select tags and not exclude tags? Works perfectly fine for me! Note that changing the publishing alist does not trigger republishing. Use C-u with the publishing command... - Carsten All the best, Tom On May 23, 2010, at 6:31 AM, Karl Martino wrote: Hi, Ah! This worked once I tried this tip Carsten - thanks! I should have realized that the buffer setting was defeating that there. You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. Eric, thanks for the tip as well. I will check out org-jekyll even though this worked because producing a blog or some kind of knowledge base from my single-org-mode-life-file sounds great :) Thanks, Karl On Sun, May 23, 2010 at 12:17 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On May 23, 2010, at 2:22 PM, Karl Martino wrote: Hi Carsten, Thanks for help, unfortunately I tried :title and it is ignored. No, it does in fact work, I just tested it. Here is the setup I used: (setq org-publish-project-alist '((ttt :base-directory ~/lib/emacs/work/org-mode/t/pub/src :base-extension org :publishing-directory ~/lib/emacs/work/org-mode/t/pub/ target :section-numbers nil :table-of-contents nil ;; :plain-source t ;; :htmlized-source t :exclude -source :title Test :title property :auto-sitemap t :makeindex t :publishing-function (org-publish-org-to-html org-publish-org-to-org You should *not* have a #+TITLE line in the buffer, and you should *not* have subtree marked - then :title is used. - Carsten The issue with #+TITLE in the buffer is that it is the same file I am exporting various times, just with different tag filters, and the title then remains the same for each export, where I want it to reflect the subset of the file, ie Karl's Work Journal, or Karl's Home Journal. A workaround that just occurred to me: I could write a method that would change the #+TITLE
Re: [Orgmode] One org file, multiple exports, is it possible?
On May 23, 2010, at 1:46 AM, Karl Martino wrote: Hello, I am a long time org-mode user, this my first time posting to the email list, and before I ask my question I first want to say thanks to all those who are helping maintain and grow this terrific software. I maintain a single org-mode file with half my life in it. It contains my journal, my task list, contacts, and notes on various projects. I use tags to indicate what content is associated to what content. What I would like to do is publish multiple html exports of this file, filtered by tag. A file that comprises of journal entries that are tagged for work. Another with journal entries that are tagged as personal highlights I want to take special note of. This file's path is at ~/notes/org/index.org. I'd like to export the filtered version of this file to ~/notes/export/index.html ~/notes/export/index_[tagname].html and to change each filtered export's title. So far in my reading of the docs, this does not seem possible. It seems you cannot indicate the export result file name. But I can indicate path. So following is a sample org-publish-project-alist that that filters by tag and puts the result in different publishing directories. But I still can't figure out how to change the title on those exported pages. Can anyone provide me with any pointers? (setq org-publish-project-alist '( (highlights :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export :publishing-function org-publish-org-to-html :select-tags (highlight) :include (index.org) I have not tried it, but if you do not have #+TITLE in the buffer, then :title This is my title in the publishing plist might work. Give it a try. - Carsten ) (work :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/work/ :publishing-function org-publish-org-to-html :select-tags (@WORK) :include (index.org) :exclude \\.org$ ) (home :base-directory ~/notes/org/ :base-extension org :publishing-directory ~/notes/export/home/ :publishing-function org-publish-org-to-html :select-tags (@HOME) :include (index.org) :exclude \\.org$ :link-up ) )) I am using org-version 6.33f and Emacs 23.1.9 on OS-X. Thank you in advance, Karl -- Seek First to Understand, Then to be Understood” - Steven Covey paradox1x.org, phillyfuture.org, @kmartino ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
