emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Touching :noexport: regions
Date: Sat, 05 May 2012 08:29:34 +0200	[thread overview]
Message-ID: <87r4uysljc.fsf@altern.org> (raw)
In-Reply-To: <86fwbf1twv.fsf@mercure.progiciels-bpi.ca> ("François Pinard"'s message of "Fri, 04 May 2012 18:08:16 -0400")

Hi François,

François Pinard <pinard@iro.umontreal.ca> 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

> 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

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.



  reply	other threads:[~2012-05-05 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 22:08 Touching :noexport: regions François Pinard
2012-05-05  6:29 ` Bastien [this message]
2012-05-05 16:04   ` François Pinard
2012-05-06  1:44     ` François Pinard
2012-05-08 12:35     ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r4uysljc.fsf@altern.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).