From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Spurious elements in HTML export
Date: Thu, 15 May 2014 11:20:41 +0200 [thread overview]
Message-ID: <CAFgFV9MbWmzgB8rzww2-NtuSP0us3z9BWGF8Bvsh_nZtp3K2KQ@mail.gmail.com> (raw)
In-Reply-To: <87wqdnv2tc.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
2014-05-15 10:55 GMT+02:00 Bastien <bzg@gnu.org>:
> Hi Fabrice,
>
> Fabrice Popineau <fabrice.popineau@gmail.com> writes:
>
> > Using the HTML exporter, I easily get spurious empty elements.
>
> I can't reproduce this. Do you have a recipe with a minimal
> configuration ?
>
>
This is already good to know!
I'll try to bisect my emacs config.
Recipe : the sole org fragment from my message in an org buffer,
and export the subtree in an html buffer with C-c C-e C-s C-b h H
> Also mention your Org and Emacs version.
>
>
Org: git latest (from today). Emacs 24.4 (trunk devel, under Windows, yeah
I know ...).
I suspect the problem might come from org-html-standalone-image-p
(incorrectly finding an image for an empty paragraph) or even from
org-string-nw-p.
What org-string-nw-p should return on a string with the single EOL
character?
BTW, I wonder if org-html-standalone-image-p does actually what is
documented. It is documented
as returning non-nil in one of two cases: element is of type paragraph or
of type link.
But its code starts with:
(and (eq (org-element-type paragraph) 'paragraph)
...)
which seems to prevent the second case. That is certainly unrelated to my
problem.
Fabrice
[-- Attachment #2: Type: text/html, Size: 2191 bytes --]
next prev parent reply other threads:[~2014-05-15 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 8:42 Spurious elements in HTML export Fabrice Popineau
2014-05-15 8:55 ` Bastien
2014-05-15 9:20 ` Fabrice Popineau [this message]
2014-05-15 9:26 ` Fabrice Popineau
2014-05-15 9:45 ` Bastien
2014-05-15 11:46 ` Nicolas Goaziou
2014-05-15 12:37 ` Fabrice Popineau
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=CAFgFV9MbWmzgB8rzww2-NtuSP0us3z9BWGF8Bvsh_nZtp3K2KQ@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.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).