emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastien.guerry@wikimedia.fr>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Worg
Date: Fri, 24 Dec 2010 15:08:56 +0100	[thread overview]
Message-ID: <87fwtnuutj.fsf@gnu.org> (raw)
In-Reply-To: <80y67feb54.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Fri, 24 Dec 2010 11:08:23 +0100")

Hi Sebastian,

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> If helpful for the future, could you tell us what it was?  

Yes - here is the commit message:

  http://repo.or.cz/w/Worg.git/commit/c7d7f1e84cf2543315f8a6e48c950167201cdaff

A #+begin_src was inside a #+begin_quote construct, which seems to
confuse the HTML exporter (as expected).

This was in org-issues.org, the most daunting file to export, not only
because it's the biggest file in Worg but also because it quotes many
examples from emails.  

> Do we have to avoid certain constructs in the Org files to avoid the
> bug to come back?

Yes, When quoting examples (in org-issues.org or elsewhere), we need to
be careful about not including syntactic elements at the wrong place.

Also, exporting Worg is made using the last Org release, not the latest
Org version from git: so anything that is exportable with bleeding-edge
Org is not always exportable with the Org version on the server.

Here is how I tracked down the problem if it helps :

- I tried to export locally with latest Org (from git) to see where 
  the export process stops: I found org-issues.org was the culprit

- I took a quick look at org-issues.org be couldn't spot the problem

- I then tried to export by first commenting out the 1st-level trees in
  org-issues.org except one: reiterated this till I found the ill-formed
  tree. 

- Then focus on this tree to find the problem.

Quick long and a bit too manual - but effective.

I added a section about this in worg-maintainance.org:

  http://orgmode.org/worg/worg-maintainance.php

(Should appear in online Worg soon.)

> Thanks and happy (holi)days to you all!

Thanks!  Happy Xmas to everyone :)

-- 
 Bastien

      reply	other threads:[~2010-12-24 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 17:47 Worg Thomas S. Dye
2010-12-23 21:36 ` Worg Bastien
2010-12-24 10:08   ` Worg Sébastien Vauban
2010-12-24 14:08     ` Bastien [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=87fwtnuutj.fsf@gnu.org \
    --to=bastien.guerry@wikimedia.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \
    /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).