Re: [O] :exclude sub folder in org-publish

2014-08-06 Thread regcl 
Bastien  writes:

> Hi,
>
> regcl  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

Re: [O] :exclude sub folder in org-publish

2014-07-28 Thread Bastien 
Hi,

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

-- 
 Bastien

Re: [O] :exclude sub folder in org-publish

2014-07-21 Thread regcl 
Bastien  writes:

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

~/A
.
+--proj
|  +--.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

Re: [O] :exclude sub folder in org-publish

2014-06-25 Thread Bastien 
regcl  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.

-- 
 Bastien

Re: [O] :exclude sub folder in org-publish

2014-06-20 Thread Nick Dokos 
regcl  writes:

> It looks like this question has been asked before, but not answered ... 
>
> Is there a way to stop the decent of org-publish at a given directory?
>
> Or, is there a syntax for including the path name of files I want to exclude?
>
> Or, maybe there something obvious I am missing?
>
> Thanks, regcl

Does

(info "(org) Selecting files")

help?

Nick

[O] :exclude sub folder in org-publish

2014-06-19 Thread regcl 
It looks like this question has been asked before, but not answered ... 

Is there a way to stop the decent of org-publish at a given directory?

Or, is there a syntax for including the path name of files I want to exclude?

Or, maybe there something obvious I am missing?

Thanks, regcl