Re: [O] Finer-grained control of published files

Brett Viren b...@bnl.gov writes: Either way, this will really help publishing from my messy source directories Thanks for testing. If nobody feels strongly against this, I'll add the feature to the master branch. -- Bastien

Re: [O] Finer-grained control of published files

Hi Brett, Brett Viren b...@bnl.gov writes: What I hope for is something equivalent to git's .gitignore functionality where I can place, say, .orgignore files full of regexp patterns anywhere in my org source tree and have org-publish honor them. I like this idea. Is there anything in this

Re: [O] Finer-grained control of published files

Bastien b...@gnu.org writes: Please test the attached patch against the tip of the master branch and let me know if it works: it checks against a .oxignore file, one regexp on each line. If you find it useful, I'll commit this for the next version. I had some unrelated trouble with the head

[O] Finer-grained control of published files

Hi, I'm trying to set up org-publish and am looking for more fine-grained control over what files get published than what (I think) I can get from configuring org-publish-project-alist. I've played with the publishing-function of org-publish-attachment and :exclude/:include and :base-extension