From: regcl <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: :exclude sub folder in org-publish Date: Wed, 06 Aug 2014 18:23:18 -0400 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Bastien's message of "Mon, 28 Jul 2014 17:49:48 +0200") Bastien <firstname.lastname@example.org> writes: > Hi, > > regcl <email@example.com> writes: > >> I could not figure out how to do this from INFO. I found examples of >> preventing publishing of specific file extensions, but not whole >> directories. > > Unless my memory fails me, :exclude works on names, not just on > extensions. So maybe using both :recursive and :exclude can lead > to what you want. Yes that matches my understanding and experience. But I could not figure out how to, for example in this tree ... ~/A . +--proj | +--.git | +--README.org | | +--Manuscript | | | +--.git | | | +--README.org | | | +--drafts | | | +--GenomicsData | | | | +--.git | | | | +--README.org ... publish the README's above GenomicsData, but not in GenomicsData. But maybe this is asking too much of org-mode publish. FWIW, I ended up using a recursive sub- make harness with something like this in the Makefile ... .PHONY: html html: README.html # export org file to html %.html: %.org emacs --batch --load=~/.emacs $*.org --eval='(org-html-export-to-html)' Best, George
prev parent reply other threads:[~2014-08-06 22:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-20 3:39 regcl 2014-06-20 15:15 ` Nick Dokos 2014-06-25 8:49 ` Bastien 2014-07-17 16:14 ` turn off monospace in src result regcl 2014-07-17 21:28 ` Andreas Leha 2014-07-17 21:38 ` Nick Dokos 2014-07-17 21:50 ` Andreas Leha 2014-07-21 19:47 ` :exclude sub folder in org-publish regcl 2014-07-28 15:49 ` Bastien 2014-08-06 22:23 ` regcl [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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: :exclude sub folder in org-publish' \ /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
Code repositories for project(s) associated with this 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).