From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Touching :noexport: regions Date: Sat, 05 May 2012 08:29:34 +0200 Message-ID: <87r4uysljc.fsf@altern.org> References: <86fwbf1twv.fsf@mercure.progiciels-bpi.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:39714) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQgkb-0002VX-5i for emacs-orgmode@gnu.org; Sat, 05 May 2012 11:18:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SQgkZ-0000wg-8u for emacs-orgmode@gnu.org; Sat, 05 May 2012 11:18:24 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:63532) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQgkZ-0000wL-06 for emacs-orgmode@gnu.org; Sat, 05 May 2012 11:18:23 -0400 Received: by wgbds1 with SMTP id ds1so2794434wgb.30 for ; Sat, 05 May 2012 08:18:21 -0700 (PDT) In-Reply-To: <86fwbf1twv.fsf@mercure.progiciels-bpi.ca> (=?iso-8859-1?Q?=22Fran=E7ois?= Pinard"'s message of "Fri, 04 May 2012 18:08:16 -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: =?iso-8859-1?Q?Fran=E7ois?= Pinard Cc: emacs-orgmode@gnu.org Hi François, François Pinard writes: > There is some machinery on my side involved into publication, which I > would rather avoid if not necessary. My little problem is that Org > checks the file time stamp, and Emacs does not distinguish, of course, > if I modify a part which is within a :noexport: region. Please don't hesitate to share it you think other people could find it useful. > The only idea I got (but I did not really torture me into this yet!) is > to maintain a kind of a cache of files before edit, and write a > specialized file comparator that would re-establish previous time stamps > when nothing publishable has been changed. Any clever idea, someone? > :-) Currently the only way to exclude an *entire* file from the publication process is to play with the :exclude parameter in `org-publish-project-alist'. We could have a #+PUBLISH: option allowing to tell whether a file should be published or not. If we had this, we could then check whether a section without the :noexport: tag has been modified... and dynamically set the buffer publication option based on this. But this is rather a complicated way, and the gain is merely about speed. If someone comes up with something more clever, let's see. Or if someone would find a new #+PUBLISH option useful outside of this use-case, let's also see. Thanks, -- Bastien