emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jason Dunsmore <emacs-orgmode@dunsmor.com>
To: Org-mode mailing list <emacs-orgmode@gnu.org>
Cc: mdl@imapmail.org
Subject: Worg now always publishing with latest Org version
Date: Fri, 29 Apr 2011 10:39:59 -0500	[thread overview]
Message-ID: <87oc3pukvk.fsf@riotblast.dunsmor.com> (raw)

Hello Worg contributors,

I've changed the Worg publishing process so that it always updates the
version of Org used to publish Worg before publishing.  Until we have a
way to gracefully handle publishing/export errors, this should help
prevent and troubleshoot the publishing errors that frequently cause
Worg to break.

* Preventing publishing errors

Locally export any document you edit as HTML (C-c C-e H) prior to
committing it to Worg and ensure the export process doesn't fail.  This
will be more reliable if you're running the latest version of Org.

You may also want to check the formatting in a browser before committing
your change (C-c C-e b).

* Troubleshooting publishing errors

If you notice Worg isn't updating, visit
http://orgmode.org/worg/publishing.txt and look for the export error
near the bottom to find the file where publishing stopped.  Locally
update to the latest version of Org, open that file, and try reproducing
the export error (C-c C-e H).  If it's not obvious where the problem is,
look at the most recent changes to the file in question:

cd Worg
git log -p org-quotes.org

Try reverting some of those changes and then re-test exporting (C-c C-e
H).

Matt,

Is there an existing page on Worg where I should put this info?

Regards,
Jason

             reply	other threads:[~2011-04-29 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 15:39 Jason Dunsmore [this message]
2011-04-29 16:47 ` Worg now always publishing with latest Org version Matt Lundin

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=87oc3pukvk.fsf@riotblast.dunsmor.com \
    --to=emacs-orgmode@dunsmor.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.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).