:exclude sub folder in org-publish

:exclude sub folder in org-publish

[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

Re: :exclude sub folder in org-publish

[Nick Dokos]

regcl <regcl@channing.harvard.edu> 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

Re: :exclude sub folder in org-publish

[Bastien]

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.

-- 
 Bastien

turn off monospace in src result

[regcl]

With this line in my .org file ...

This is src_R{foo<-"FOO"; paste(foo)}.

... when I publish to html or pdf, I get ...

This is FOO.

... which is wonderful, except that "FOO" is monospace.  

Can I turn off monospace for all results of inline source?

Thanks,
regcl

Re: turn off monospace in src result

[Andreas Leha]

Hi regcl,

regcl <regcl@channing.harvard.edu> writes:

> With this line in my .org file ...
>
> This is src_R{foo<-"FOO"; paste(foo)}.
>
> ... when I publish to html or pdf, I get ...
>
> This is FOO.
>
> ... which is wonderful, except that "FOO" is monospace.  
>
> Can I turn off monospace for all results of inline source?

I do not know, how to do that for all inline source blocks.  But you can
turn it off
1. per code block as in src_R[:results raw]{foo<-"FOO"; paste(foo)}
2. globally for all block as in '#+PROPERTY: results raw'
   (then you would override this setting per non-inline code block)

HTH,
Andreas

Re: turn off monospace in src result

[Nick Dokos]

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Hi regcl,
>
> regcl <regcl@channing.harvard.edu> writes:
>
>> With this line in my .org file ...
>>
>> This is src_R{foo<-"FOO"; paste(foo)}.
>>
>> ... when I publish to html or pdf, I get ...
>>
>> This is FOO.
>>
>> ... which is wonderful, except that "FOO" is monospace.  
>>
>> Can I turn off monospace for all results of inline source?
>
> I do not know, how to do that for all inline source blocks.  But you can
> turn it off
> 1. per code block as in src_R[:results raw]{foo<-"FOO"; paste(foo)}

Looks like

--8<---------------cut here---------------start------------->8---
This is src_R[:results raw]{foo<-"FOO"; paste(foo)}.
--8<---------------cut here---------------end--------------->8---

produces a newline after the evaluated code block in the HTML file,
which is rendered as a space between the word FOO and the period.  Bug?

Nick

Re: turn off monospace in src result

[Andreas Leha]

Hi Nick,

Nick Dokos <ndokos@gmail.com> writes:

> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> Hi regcl,
>>
>> regcl <regcl@channing.harvard.edu> writes:
>>
>>> With this line in my .org file ...
>>>
>>> This is src_R{foo<-"FOO"; paste(foo)}.
>>>
>>> ... when I publish to html or pdf, I get ...
>>>
>>> This is FOO.
>>>
>>> ... which is wonderful, except that "FOO" is monospace.  
>>>
>>> Can I turn off monospace for all results of inline source?
>>
>> I do not know, how to do that for all inline source blocks.  But you can
>> turn it off
>> 1. per code block as in src_R[:results raw]{foo<-"FOO"; paste(foo)}
>
> Looks like
>
> This is src_R[:results raw]{foo<-"FOO"; paste(foo)}.
>
> produces a newline after the evaluated code block in the HTML file,
> which is rendered as a space between the word FOO and the period.  Bug?
>

I tend to agree.  There was some discussion on this last year [fn:1] that went
dead after a while.  I still think that modifying raw results (as in
adding newline) should be avoided -- at least in inline source blocks.

Regards,
Andreas



Footnotes:

[fn:1] http://article.gmane.org/gmane.emacs.orgmode/71385

Re: :exclude sub folder in org-publish

[regcl]

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

~/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: :exclude sub folder in org-publish

[Bastien]

Hi,

regcl <regcl@channing.harvard.edu> 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: :exclude sub folder in org-publish

[regcl]

Bastien <bzg@gnu.org> writes:

> Hi,
>
> regcl <regcl@channing.harvard.edu> 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