>
> > 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?
>
> Yes, the name given to the results block doesn't depend on the results
> keyword. You can give it any name, as long as it is unique.
>
> H
Vikas Rawal writes:
>> > 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 wa
> > 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.
>
> W
Hello,
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
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,
>
> 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 blo
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.
Vikas, can you try this? Simply add a name to the generated table when
you also add a ca
> I confirm the same behavior, in ODT and HTML, and think it's a
> bug. Additional info:
>
> Vikas Rawal didn't say if he also added a `#+NAME: foo' line above the
> generated table. I expected that to solve it, so I tried. This did give
> the table an `id="foo"' attribute on HTML export for a c
Hi,
I confirm the same behavior, in ODT and HTML, and think it's a
bug. Additional info:
Vikas Rawal didn't say if he also added a `#+NAME: foo' line above the
generated table. I expected that to solve it, so I tried. This did give
the table an `id="foo"' attribute on HTML export for a cross-ref
I had raised this on the mailing list earlier but my problem has not
been resolved. I shall be grateful if somebody could help debug.
My org-version is:
Org-mode version 8.0-pre(release_8.0-pre-247-gbc3ccd @
/home/vikas/lisp/org-mode/lisp/)
When I have a named source block (say crop_median), I
10 matches
Mail list logo
