[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] exporting cross-references to source block results CORRECTION
From: |
Vikas Rawal |
Subject: |
Re: [O] exporting cross-references to source block results CORRECTION |
Date: |
Thu, 11 Apr 2013 17:48:41 +0530 |
User-agent: |
Mutt/1.5.21 (2012-12-30) |
> > cross-reference will pick that up correctly.
> >
> > 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.
>
> We are misunderstanding each other.
>
> #+results are never used for cross-references. This is a Babel internal
> keyword used to refer to the source that generated this element.
>
> Cross-references only react to #+name keyword.
>
Sorry, this is confusing. Is it then the case that we are naming the
source block to ensure that captions stick to the corresponding
results block? And then, we need to separately name the results block,
and use a different name for it, so that the cross-references pick it
up correctly?
Vikas
- [O] exporting cross-references to source block results, Vikas Rawal, 2013/04/11
- Re: [O] exporting cross-references to source block results, Christian Moe, 2013/04/11
- Re: [O] exporting cross-references to source block results, Vikas Rawal, 2013/04/11
- Re: [O] exporting cross-references to source block results CORRECTION, Christian Moe, 2013/04/11
- Re: [O] exporting cross-references to source block results CORRECTION, Vikas Rawal, 2013/04/11
- Re: [O] exporting cross-references to source block results CORRECTION, Christian Moe, 2013/04/11
- Re: [O] exporting cross-references to source block results CORRECTION, Nicolas Goaziou, 2013/04/11
- Re: [O] exporting cross-references to source block results CORRECTION,
Vikas Rawal <=
- Re: [O] exporting cross-references to source block results CORRECTION, Nicolas Goaziou, 2013/04/11
- Re: [O] exporting cross-references to source block results CORRECTION, Vikas Rawal, 2013/04/11