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: Wed, 18 Apr 2012 17:18:36 +0200 [thread overview]
Message-ID: <8062cxukz7.fsf@somewhere.org> (raw)
In-Reply-To: 87ty0txiwh.fsf@gnu.org
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> 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?
>
> I guess that's because not everybody uses org-special-blocks.el as a
> module.
By "using org-special-blocks.el as a module", if you mean "having a line such
as":
(add-to-list 'org-modules 'org-special-blocks)
I did not have one either.
I just had:
(require 'org-special-blocks)
But, IIUC, that's more or less equivalent:
- being in `org-modules' means that the package will be required[1] many times
before trying to do different operations (such as inserting a link, etc.),
and that there is a protection mechanism in case the package can't be loaded
- being explicitly required in my .emacs does only try to load it once.
Apart from that, I don't see differences.
> The ERT suite doesn't make any test against this.
Well against exporting HTML. But I did not realize that I was more or less the
only one in the world ;-) to load `org-special-blocks'[2] while exporting to HTML.
This must explain that. Case is closed.
Best regards,
Seb
Footnotes:
[1] Though, really only loaded once.
[2] And I must admit I maybe have used it once or twice, not more... Though, I
still find it an interesting feature.
--
Sebastien Vauban
prev parent reply other threads:[~2012-04-18 15:18 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
2012-04-09 11:07 ` Bastien
2012-04-18 15:18 ` Sebastien Vauban [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=8062cxukz7.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).