From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Viren Subject: Finer-grained control of published files Date: Sun, 09 Mar 2014 10:56:20 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37163) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMf9o-0007Yi-GA for emacs-orgmode@gnu.org; Sun, 09 Mar 2014 10:57:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WMf9f-0000wE-QX for emacs-orgmode@gnu.org; Sun, 09 Mar 2014 10:56:52 -0400 Received: from smtpgw.bnl.gov ([2620:10a:0:3::30]:43484 helo=iron3.sec.bnl.local) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WMf9f-0000uE-Lv for emacs-orgmode@gnu.org; Sun, 09 Mar 2014 10:56:43 -0400 Received: from bviren by lycastus.phy.bnl.gov with local (Exim 4.80) (envelope-from ) id 1WMf9I-0003VB-Oe for emacs-orgmode@gnu.org; Sun, 09 Mar 2014 10:56:20 -0400 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain 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 regexps. What I'm finding is that I want to control what type of files get published on almost a per-directory basis and different directories may have mutually conflicting file patterns to include/exclude. Creating a new org-publish-project-alist entry for each is tedious. 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. Is there anything in this direction? Thanks, -Brett. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlMcgRQACgkQEixH2Z0dKCwliACgpe43G41UqXXFKN76YJ88QuTN 3s8AnAukC4AytYq/vFSpJ1wnHh0oFXs+ =6eqN -----END PGP SIGNATURE----- --=-=-=--