emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Christian Moe <mail@christianmoe.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: exporting cross-references to source block results CORRECTION
Date: Thu, 11 Apr 2013 13:31:15 +0200	[thread overview]
Message-ID: <m21uahwbgc.fsf@christianmoe.com> (raw)
In-Reply-To: <20130411104605.GA28852@panahar>


Vikas Rawal writes:
>> Oops, sorry, I take back my last message, there was an error in my test
>> example.
>> 
>> Adding a #+NAME above the generated table DOES result in a correct
>> cross-reference. That seems like reasonable behavior to me.
>
> The intended behaviour, as documented by Nicolas, is that a named
> source block will result in output with #+RESULTS, and that the
> cross-reference will pick that up correctly.

I confirm that I don't get a correct cross-reference to a table that
is identified only by its #+RESULTS name.

> If #+RESULT is not to work, it is better to change
> org-babel-results-keyword to NAME, and then what you are suggesting
> happens automatically. But in the earlier thread on the topic, Nicolas
> said that was not the right way.

I see. Sorry for not following the discussion. In that way, you get both
code block and result identified by the same NAME line, and Babel
appears to be smart enough to handle that without the code block
overwriting itself...

But this solution gives faulty exports if you're exporting both code and
results (`:exports both'). In HTML, you get two different elements with
the same id attribute, the code block and the table. That shouldn't
happen. I find Firefox resolves the conflict by jumping to whichever of
the two elements appears first.

It seems to me that you would have the same problem even if the exporter
did pick up the name from the RESULTS line and make a cross-reference to
it, as you expect it to. The target would still be ambiguous.

I submit that the best way to get a cross-reference to a generated table
in all circumstances is to manually name that table with a #+NAME line
and a *unique* name, i.e. *different* from that of the source block that
generated it. This seems a reasonable requirement.

Yours,
Christian

next prev parent reply	other threads:[~2013-04-11 11:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11  8:46 exporting cross-references to source block results Vikas Rawal
2013-04-11  9:42 ` Christian Moe
2013-04-11  9:57   ` Vikas Rawal
2013-04-11 10:37     ` exporting cross-references to source block results CORRECTION Christian Moe
2013-04-11 10:46       ` Vikas Rawal
2013-04-11 11:31         ` Christian Moe [this message]
2013-04-11 12:00         ` Nicolas Goaziou
2013-04-11 12:18           ` Vikas Rawal
2013-04-11 14:30             ` Nicolas Goaziou
2013-04-11 15:24               ` Vikas Rawal

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=m21uahwbgc.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vikaslists@agrarianresearch.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

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