From: Matt Price <moptop99@gmail.com>
To: org mode <emacs-orgmode@gnu.org>
Subject: Re: org-reveal questions
Date: Mon, 26 Oct 2015 12:34:26 -0400 [thread overview]
Message-ID: <CAN_Dec-St++bbL55b5zFTeUCfAj6mktY31nVWRe7C=M5SZjO3Q@mail.gmail.com> (raw)
In-Reply-To: <CAN_Dec8mWrQz2gYeYu1Vy_krT0Jzw1sbfEHEi6522RmSt-CDrQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Sun, Oct 25, 2015 at 6:01 PM, Matt Price <moptop99@gmail.com> wrote:
>
>
> On Sun, Oct 25, 2015 at 4:46 PM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> The second problem is more about HTML export than reveal
>> specifically. In LaTeX, an image is exported directly without any
>> surrounding material if only the image is there. Surrounding material,
>> i.e. LaTeX figure environment, is only included if a caption is
>> present. In reveal, there doesn't seem to be an equivalent
>> behaviour. That is, all my images get exported within a figure
>> <div>. I would like to have the option of a bare-bones <img> export
>> without having to resort to direct HTML. Is this possible? It would
>> seem to make sense to have the same type of logic apply to HTML export
>> as it does to LaTeX?
>>
>> I doubt this is possible in reveal right now but it shouldn't be too hard
> to add a (switch ) statement that exports a naked img if some condition is
> met. And I et a relevant patch could be submitted as a feature request.
>
>
Rereading this, I think maybe you should post this to a list as a question
about the html exporter, not org-reveal. Nicolas and others may have
thoughts on the logic of the difference. The difference may reside in
differing expectations/standards in latex & html.
m
>
>
[-- Attachment #2: Type: text/html, Size: 2291 bytes --]
next prev parent reply other threads:[~2015-10-26 16:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 5:16 org-reveal questions Xebar Saram
2015-10-23 6:18 ` Eric S Fraga
2015-10-23 6:45 ` Xebar Saram
2015-10-23 8:39 ` Eric S Fraga
2015-10-23 9:09 ` Fabrice Popineau
2015-10-23 9:20 ` Xebar Saram
2015-10-23 14:58 ` Matt Lundin
2015-10-23 16:08 ` Matt Price
2015-11-22 14:25 ` Xebar Saram
2015-11-22 15:50 ` Eric S Fraga
2015-11-22 16:47 ` Xebar Saram
2015-11-22 21:58 ` Matt Price
2015-11-23 2:55 ` John Hendy
2015-12-03 9:07 ` Xebar Saram
2015-12-04 14:55 ` John Hendy
2015-12-04 15:49 ` Xebar Saram
2015-12-04 18:52 ` John Hendy
2015-12-03 9:10 ` Xebar Saram
2015-10-23 13:27 ` Andreas Leha
2015-10-23 16:15 ` Matt Price
2015-10-25 20:46 ` Eric S Fraga
2015-10-25 22:01 ` Matt Price
2015-10-26 16:34 ` Matt Price [this message]
2015-10-27 14:41 ` Eric S Fraga
2015-10-26 15:43 ` Xebar Saram
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='CAN_Dec-St++bbL55b5zFTeUCfAj6mktY31nVWRe7C=M5SZjO3Q@mail.gmail.com' \
--to=moptop99@gmail.com \
--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).