emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: "Diez B. Roggisch" <deets@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: HTML export to just a single file?
Date: Tue, 22 Apr 2014 11:51:45 +0200	[thread overview]
Message-ID: <87eh0padzi.fsf@bzg.ath.cx> (raw)
In-Reply-To: <046B4215-73E9-4D15-B998-3B02F499CCBE@web.de> (Diez B. Roggisch's message of "Tue, 22 Apr 2014 11:40:56 +0200")

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

Hi Diez,

"Diez B. Roggisch" <deets@web.de> writes:

> Cool! Where can I get the fix?

From the maint branch of the Git repository.
Or just wait for the new release.

>> Next time please try to find the minimal file where the bug happens:
>> that way you won't have to put example files in Dropbox (those files
>> will not be accessible one day), and you would have been able to give
>> more useful information on what is wrong.
> I could have attached them - but I didn't know the policies here.
> Also, I thought they were quite minimal ;) The .org is one KB ;)
> What could be stripped?

Nearly everything :)

I attach the minimal file that produces the bug.

Had you send this, I'd have (and you'd have) immediately seen the
problem comes from the empty #+INFOJS_OPT line.

Anyway, next time!

[-- Attachment #2: test.org --]
[-- Type: application/vnd.lotus-organizer, Size: 38 bytes --]

[-- Attachment #3: Type: text/plain, Size: 14 bytes --]


  reply	other threads:[~2014-04-22  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 15:55 HTML export to just a single file? Diez B. Roggisch
2014-04-17 15:59 ` Bastien
2014-04-17 16:20   ` Diez B. Roggisch
2014-04-17 16:25     ` Bastien
2014-04-22  8:33       ` Diez B. Roggisch
2014-04-22  8:44         ` Bastien
2014-04-22  9:40           ` Diez B. Roggisch
2014-04-22  9:51             ` Bastien [this message]
2014-04-17 19:37 ` J. David Boyd

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:

  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=87eh0padzi.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=deets@web.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).