From: Matt Lundin <mdl@imapmail.org>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: Jason Dunsmore <emacs-orgmode@dunsmor.com>,
Org Mode List <emacs-orgmode@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Worg publishing broken?
Date: Thu, 17 Feb 2011 11:27:49 -0500 [thread overview]
Message-ID: <87r5b6mxru.fsf@fastmail.fm> (raw)
In-Reply-To: <871v38gceg.fsf@gnu.org> (Bastien's message of "Wed, 16 Feb 2011 17:41:27 +0100")
Bastien <bastien.guerry@wikimedia.fr> writes:
> Hi Jason,
>
> Jason Dunsmore <emacs-orgmode@dunsmor.com> writes:
>
>>> I have today pushed two updates onto Worg which have not yet been published.
>>> Maybe Worg publishing is currently broken?
>>
>> A recently-added section on the FAQ was using "shell" as the mode of a
>> source block instead of "sh". I fixed it and re-pulled/published
>> Worg.
>
> My bad, I added this.
>
> Thanks for the fix!
Would there be any way to get the Worg publishing script or export of
source code blocks to fail gracefully in these instances? This same
issue came up a couple of weeks ago with a new tutorial. A mislabeled
source code block brought the whole publishing process to a halt.
One idea: instead of always throwing an error,
org-export-replace-src-segments-and-examples might contain an option to
replace BEGIN_SRC...END_SRC with BEGIN_EXAMPLE...END_EXAMPLE if no
source block is found.
Best,
Matt
next prev parent reply other threads:[~2011-02-17 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:17 Worg publishing broken? Carsten Dominik
2011-02-16 16:30 ` Bastien
2011-02-16 16:34 ` Jason Dunsmore
2011-02-16 16:41 ` Bastien
2011-02-17 16:27 ` Matt Lundin [this message]
2011-02-18 8:58 ` Bastien
2011-02-18 16:19 ` Jason Dunsmore
2011-02-18 18:05 ` Jambunathan K
2011-02-19 1:09 ` Bastien
[not found] ` <87pqqosucm.fsf-mXXj517/zsQ@public.gmane.org>
2011-02-19 14:04 ` Sébastien Vauban
2011-02-22 11:53 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5b6mxru.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=bastien.guerry@wikimedia.fr \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@dunsmor.com \
--cc=emacs-orgmode@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.