With the latest push to the git repo,
you can use $LR1, $LR2, ... to reference fields in the last row.
HTH
- Carsten
On Dec 18, 2008, at 11:14 PM, Carsten Dominik wrote:
Hi all,
thanks for your constructive contributions to the thread.
However, I will still reverse the change that introdu
Hi all,
thanks for your constructive contributions to the thread.
However, I will still reverse the change that introduced @0 as a
reference to the last line. The risk that someone will be bitten by
this is too high, and @0 is really too similar to @+0, so I think the
distinction is not l
How about adding a customizable variable which defaults to nil. (Call
it org-use-new-spreadsheet-semantics). If it is nil, whenever the new
syntax is used, raise a warning.
The warning could be:
1. just a message to the echo area
2. inserted into the top of the updated table
3. an error which
For me the new behaviour is fine, if leaving out the row specification works.
The distinction between @0 and @+0 would work, too, but is rather confusing and
hard to remember. I think both should represent either the last or the current
row.
Greetings,
Stephan
Carsten Dominik wrote:
>
You are right, this is an incompatible change. Dammit.
What should do? Opinions?
The problem is that this change may lead to older tables
evaluated incorrectly. I do like the new convention and
think that @+0 or leaving out the row specifications are
good alternatives - but maybe we are obl
Hello,
the reference to the last row @0 led to incompatible changes:
* spreadsheet: relative reference to same row
(using Org mode version 6.15d)
The Org mode version 6.15 introduced @0 as a reference to the last
row for spreadsheet (org-table) formulas. This leads to problems if
you us
