emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: html export
Date: Sun, 20 Jun 2010 06:11:17 -1000	[thread overview]
Message-ID: <48C8312A-7793-49D0-AA26-24AB15AC662F@tsdye.com> (raw)
In-Reply-To: <871vc28js3.fsf@gmail.com>

Hi Eric,

On Jun 19, 2010, at 5:28 PM, Eric Schulte wrote:

> Hi Tom,
>
> "Thomas S. Dye" <tsd@tsdye.com> writes:
>
>> Aloha all,
>>
>> Exporting this small file to html here doesn't put a caption on the
>> figure.
>>
>> * No caption
>>
>> #+CAPTION: Histogram of adze weights on a logarithmic scale
>> #+LABEL: fig:wt-log
>>
>> [[file:~/Public/projects/903_adzes/r/sr-nb-scatter.png]]
>>
>> Does anyone else see this?
>>
>
> Try removing the empty line between the #+LABEL:... line and the
> [[file:... line, that worked for me.  or rather the following worked  
> for
> me
>
> --8<---------------cut here---------------start------------->8---
> * No caption
>
> #+CAPTION: Histogram of adze weights on a logarithmic scale
> #+LABEL: fig:wt-log
> [[file:graph.png]]
>
> --8<---------------cut here---------------end--------------->8---
>
> also, if the file doesn't exist, then neither the file, nor the  
> label or
> caption will export.
>
>>
>> All of a sudden, I'm having the devil's own time with html export.  I
>> made small changes to a large export project file and was surprised
>> when none of the links were exported.  The project has been exporting
>> perfectly for months now.
>>
>
> I agree it seems that the html export has been a little bit less  
> stable
> as of late.
>
> Best -- Eric

Removing the blank line doesn't work for me either.

Org-mode version 6.36trans (release_6.36.291.gaf90f)

Ah, I'm finally able to reproduce the problem in my larger file.  Here  
is an example:

* No results exported

#+srcname: problem
#+begin_src R
   b <- 4
#+end_src

#+results: problem
[[file:~/Public/projects/903_adzes/r/sr-nb-scatter.png]]

The key is that srcname: and results: have the same name.  Changing  
the results: name works.

* Results exported

#+srcname: problem
#+begin_src R
   b <- 4
#+end_src

#+results: problem-not
[[file:~/Public/projects/903_adzes/r/sr-nb-scatter.png]]

All the best,
Tom

  parent reply	other threads:[~2010-06-20 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20  1:50 html export Thomas S. Dye
2010-06-20  3:28 ` Eric Schulte
2010-06-20  3:58   ` Nick Dokos
2010-06-20 16:11   ` Thomas S. Dye [this message]
2010-06-20 18:14     ` Eric Schulte
2010-06-20 20:17       ` Nick Dokos
2010-06-20 20:54       ` Thomas S. Dye
  -- strict thread matches above, loose matches on Subject: below --
2010-05-27 16:37 Thomas S. Dye
2010-05-27 20:58 ` Carsten Dominik
2010-05-27 21:29   ` Sebastian Rose

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=48C8312A-7793-49D0-AA26-24AB15AC662F@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    /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).