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 explanation.  I don't do much attaching these days.
Here is the file again as a proper attachment. 

* Test with block names containing a colon
** Data
My data can be found in Table [[tab:my_data]].
#+CAPTION: My data
#+NAME: tab:my_data
| a | b |
| 2 | 4 |
| 3 | 9 |

** Code

My code can be found in Listing [[code:my_code]].

#+CAPTION: My code
#+NAME: code:my_code
#+HEADER: :var data=tab:my_data :colnames yes
d <- data

** Results

My results can be found in Table [[tab:my_results]].

#+CAPTION: My results
#+NAME: tab:my_results
#+RESULTS: code:my_code
| a | b |
| 2 | 4 |
| 3 | 9 |

** Conclusions

Names with colons don't work.

>> Reading with Gnus, I don't see any blank lines between the table
>> info and the table itself.
> It depends on your Gnus configuration. If you set
>    (setq gnus-inhibit-mime-unbuttonizing t)
> then at least my version of Gnus (v5.13) does indeed split the buffer
> in multiple pieces with additional newlines.

I haven't customised gnus-inhibit-mime-unbuttonizing and it has the
value 'nil'.

If I read the thread via

there are also no extra newlines.  Does anyone else apart from Eric also
see space between table header and table?

BTW, I'm still more interested in the colon thing ...

This signature is currently under construction.

Reply via email to