From: Fabrice Niessen <fni-news-TA4HMoP+1wHrZ44/DZwexQ@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Publishing on Worg succeeds or fails? -- I can't say!
Date: Wed, 22 Apr 2015 22:11:08 +0200 [thread overview]
Message-ID: <867ft3x6sj.fsf@example.com> (raw)
In-Reply-To: 87mw20c4rx.fsf@nicolasgoaziou.fr
Nicolas Goaziou wrote:
> Fabrice Niessen writes:
>
>> Could that be stated clearly in the output?
>
> You should ask to whom implemented Worg.
And that is? Bastien?
>> The thing is that I did not touch those links, as you can see in my
>> commit. So, somehow, Org became more strict. And the fact that that
>> file wasn't modified for some time means it wasn't re-exported for
>> the same period; hence, the problem was never found -- until someone
>> modifies whatever in the file...
>
> Correct.
>
>> IOW, shouldn't all files be published each time, to spot such
>> problems as soon as they become problems (because of syntax changes,
>> for example), instead of being much later, whenever the file is
>> changed (if it ever is)?
>
> So you get 50-100 files to fix instead of the one you modified?
No much fun, that's right.
> IMO, it would be a waste to re-publish unmodified files. You only have
> to consider syntax changes when updating a file.
OTOH, I find it uncomfortable to have a "project" (in the publishing
sense) which is, in fact, not publishable anymore, because many files
won't export anymore -- some could even still rely on Org 7...
But I understand your point. The question comes down to what we want:
a uniform, coherent set of Org files (all up-to-date, and exportable) or
a set of HTML pages which we don't touch anymore if their Org
counterpart is not touched either.
> Note that you need to have a very recent Org (less than 7 hours) to use
> it.
Fixed the problems. Now that page is up-to-date on Worg again. Thanks.
Best regards,
Fabrice
--
Fabrice Niessen
Leuven, Belgium
http://www.pirilampo.org/
prev parent reply other threads:[~2015-04-22 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 18:37 Publishing on Worg succeeds or fails? -- I can't say! Fabrice Niessen
2015-04-22 19:33 ` Nicolas Goaziou
2015-04-22 19:46 ` Fabrice Niessen
2015-04-22 20:00 ` Nicolas Goaziou
2015-04-22 20:11 ` Fabrice Niessen [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=867ft3x6sj.fsf@example.com \
--to=fni-news-ta4hmop+1whrz44/dzwexq@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).