Nicolas Goaziou writes:
> Hello,
>
> "Loris Bennett" writes:
>
>> BTW, I'm still more interested in the colon thing ...
>
> Babel apparently supports (undocumented) "filename:reference" syntax for
> foreign references. In your case, "tab:my_data" is mistakenly seen as
> a reference to "my_data"
Hello,
"Loris Bennett" writes:
> BTW, I'm still more interested in the colon thing ...
Babel apparently supports (undocumented) "filename:reference" syntax for
foreign references. In your case, "tab:my_data" is mistakenly seen as
a reference to "my_data" in the file "tab".
As a safety measure,
"Loris Bennett" writes:
> Hi,
>
> I want to export to LaTeX and refer to tables and code blocks as in the
> example below. However a name with a colon, such as 'tab:my_data' used
> as a variable for a source block fails:
>
> org-babel-ref-resolve: Reference 'my_data' not found in this buffer
>
On Friday, 13 Feb 2015 at 13:36, Loris Bennett wrote:
> Stefan Nobis writes:
>
>> "Loris Bennett" writes:
>>
>>> The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'.
>>
>> But you attached it as inline, so the same problems could arise. To be
>> sure to transfer the file unmodifi
Stefan Nobis writes:
> "Loris Bennett" writes:
>
>> The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'.
>
> But you attached it as inline, so the same problems could arise. To be
> sure to transfer the file unmodified, choose "attachment" as
> disposition.
Thanks for that expl
"Loris Bennett" writes:
> The above was attached with Gnus 'C-c RET f', MIME type 'text/x-org'.
But you attached it as inline, so the same problems could arise. To be
sure to transfer the file unmodified, choose "attachment" as
disposition.
> Reading with Gnus, I don't see any blank lines betwe
"Loris Bennett" writes:
> Eric S Fraga writes:
>
>> On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote:
>>
>> [...]
>>
>>> In my ECM and in my original posting there are no empty lines between
>>> the table information and the actual table (see attached screenshot of
>>> my original ECM). How
Eric S Fraga writes:
> On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote:
>
> [...]
>
>> In my ECM and in my original posting there are no empty lines between
>> the table information and the actual table (see attached screenshot of
>> my original ECM). However, I can see that in your quoted
On Friday, 13 Feb 2015 at 08:49, Loris Bennett wrote:
[...]
> In my ECM and in my original posting there are no empty lines between
> the table information and the actual table (see attached screenshot of
> my original ECM). However, I can see that in your quoted version above
> there is one.
U
Hi Eric,
Eric S Fraga writes:
> On Thursday, 12 Feb 2015 at 16:19, Loris Bennett wrote:
>> Hi,
>>
>> I want to export to LaTeX and refer to tables and code blocks as in the
>> example below. However a name with a colon, such as 'tab:my_data' used
>> as a variable for a source block fails:
>>
>>
On Thursday, 12 Feb 2015 at 16:19, Loris Bennett wrote:
> Hi,
>
> I want to export to LaTeX and refer to tables and code blocks as in the
> example below. However a name with a colon, such as 'tab:my_data' used
> as a variable for a source block fails:
>
> org-babel-ref-resolve: Reference 'my_data
11 matches
Mail list logo
