emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] void-variable org-special-blocks-line when exporting to HTML
Date: Fri, 06 Apr 2012 12:04:54 +0200	[thread overview]
Message-ID: <80iphddvll.fsf@somewhere.org> (raw)
In-Reply-To: 874nsxi63l.fsf@gnu.org

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> In other words, my HTML export is completely broken for any file.
>
> It should be fixed now.

It is!  Thanks a lot.

> I hope this was the last problem in this
> yeahhh-let's-fix-new-Emacs-warning-and-replace-them-with-plain-bugs-instead
> saga...
>
>> I'm totally in the blue -- maybe a sign that I need holidays?  ;-)
>
> A sign that *I* need holidays!

I'm not out of the blue yet... I still can't understand why:

- you were unable to reproduce it?
  What's the difference between you and me? ;-)
  I mean why does Org behave differently between us?

- nobody else seemed hit by this?
  I'm surprised by the absence of reactions while HTML export was completely
  failing for a couple of days. Once again, why only me?

- this wasn't trapped by the ERT test suite?
  There are a lot of HTML exports done in the tests. Why did they succeed?

Have you hints on this?

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-04-06 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  9:51 [bug] void-variable org-special-blocks-line when exporting to HTML Sebastien Vauban
2012-04-05 10:31 ` Bastien
2012-04-06  1:09   ` Vladimir Lomov
2012-04-06  8:28     ` Sebastien Vauban
2012-04-06  9:04       ` Bastien
2012-04-06 10:04         ` Sebastien Vauban [this message]
2012-04-09 11:07           ` Bastien
2012-04-18 15:18             ` Sebastien Vauban

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=80iphddvll.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@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).