emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: regcl <regcl@channing.harvard.edu>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: :exclude sub folder in org-publish
Date: Mon, 21 Jul 2014 15:47:41 -0400	[thread overview]
Message-ID: <qrh7g36v6hu.fsf@channing.harvard.edu> (raw)
In-Reply-To: <8761jpl6gl.fsf@bzg.ath.cx> (Bastien's message of "Wed, 25 Jun 2014 10:49:14 +0200")

Bastien <bzg@gnu.org> writes:

> regcl <regcl@channing.harvard.edu> writes:
>> Or, maybe there something obvious I am missing?
> Please tell us what you wanted to do, show us what you tried by
> sharing parts of your configuration, and we'll be able to help.

When my .org file points to a second .org file in a directory below, and
with ...

:publishing-function org-html-publish-to-html
:recursive t

... the sub directory gets published. I am no clear of whether this is
triggered by the references to the .org file below, or simply by
":recursive t."

In any event, this is generally a good thing, except that there are
situations where I would like to prevent recursion into specific
sub-directories. For example, consider the tree below, and that I want to
publish proj and Manuscript, but not GenomicsData ...

|  +--.git
|  +--README.org
|  |  +--Manuscript
|  |  |  +--.git
|  |  |  +--README.org
|  |  |  +--drafts
|  |  |  +--GenomicsData
|  |  |  |  +--.git
|  |  |  |  +--README.org

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.

Thanks, regcl

  parent reply	other threads:[~2014-07-21 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  3:39 :exclude sub folder in org-publish 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   ` regcl [this message]
2014-07-28 15:49     ` :exclude sub folder in org-publish Bastien
2014-08-06 22:23       ` regcl

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=qrh7g36v6hu.fsf@channing.harvard.edu \
    --to=regcl@channing.harvard.edu \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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 public inbox


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).