Hi François,
François Pinard pin...@iro.umontreal.ca writes:
But I feel this would be gross, absolute overkill
I do feel the same -- especially because, again, the issue at stake is
the time it takes to publish the files to HTML. One idea would be to
gather as much :noexport: subtrees into a
Hi François,
François Pinard pin...@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
Bastien b...@gnu.org writes:
Hi François,
Bonjour chez vous! :-)
François Pinard pin...@iro.umontreal.ca writes:
There is some machinery on my side involved into publication, which I
would rather avoid if not necessary.
Please don't hesitate to share it you think other people could find
François Pinard pin...@iro.umontreal.ca writes:
Our dear Bastien writes:
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
Hi, people. I doubt there is an easy solution, but here I go nevertheless.
Many of my Org notes are published to the Web, which have :noexport:
headers. It is very convenient that Org allows me to keep all parts
together, whether parts are published or not, in a single Org file.
There is some
