From: Ian Barton <firstname.lastname@example.org>
Subject: Re: Error When Publishing a Single File
Date: Tue, 17 Feb 2009 12:46:46 +0000 [thread overview]
Message-ID: <499AB1B6.email@example.com> (raw)
> Ian Barton <firstname.lastname@example.org> writes:
>> This has been happening for a while. I suspect it's something in my settings,
>> but I can't work out what. When I publish a single file, I get the following
> Since this feature is prone to error, I'd suggest to drop it entirely. I
> never use it here. Instead, I'd suggest to change the publishing feature
> as follows:
> a) The index file generation takes quite a long time. As for me , this
> is the only reason to keep this single page publishing.
> So why not just generate the index file, if _new_ (as opposed to
> changed) files are found in the project?
> Otherwise ask.
> b) Interactive publishing
> Some times it might be desirable to not publish all changes at
> once (e.g. do not publish unfinished changes).
> The publishing mechanism could ask for every file. This could be
> bound to `C-u C-e P' or `C-c C-e i' for example.
> c) Is it possible to extend the publising-timestamp mechanism to
> exported blocks? E.g. ditaa images take quite some time to
I too would be happy if something like this could be implemented. Like
Sebastian I only use the single file feature to save time.
next prev parent reply other threads:[~2009-02-17 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 11:21 Ian Barton
2009-02-17 11:43 ` Sebastian Rose
2009-02-17 12:46 ` Ian Barton [this message]
2009-02-19 19:22 ` Carsten Dominik
2009-02-17 12:25 ` Matthew Lundin
2009-02-26 21:18 ` Carsten Dominik
2009-02-27 8:06 ` Ian Barton
2009-02-27 8:25 ` Sebastian Rose
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 \
* 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).