Yes, that fixed it. Thanks!
Yours,
Christian
On 10/27/11 6:13 PM, Carsten Dominik wrote:
This should be fixed now, please verify.
Thanks!
- Carsten
Hi Wu Feng,
thank your for this rather clear bug report, even including the correct
analysis. And Christian, thanks for confirming that this is a bug.
As already suggested by Wu Feng, this error is caused by a premature
expansion of @>$1, while still inside the context of table 2. In that
conte
Reproduced. I think this qualifies as a bug.
Yours,
Christian
Hello,
First, please check below simple example, I defined two tables (T1 and
T2). In table-2, I remotely refer to the @>$1 (last row, column 1) and
$LR2 (last row, column 2) of T1.
#+TBLNAME: T1
| 11 | 12 |
| 21 | 22 |
| 31 | 32 |
#+TBLNAME: T2
| xxx | xxx | xxx | xxx |
| # | 21 | 32 |
