On 10.5.2012, at 09:15, Tobias wrote: > First I have to apologize for posting the bug report twice. The first report > has > been sent from my company. I thought that this bug-report does not make it to > the list because the e-mail address at my company is not subscribed to the > list. > Therefore, I subscribed with my private e-mail address and sent the bug report > once more. > > Now, some digging about the bug. I have investigated org-table-recalculate and > the functions called therein. > > The only place where @II is handled correctly is: > org-table-get-descriptor-line > This function is only called within: > org-table-get-range > This function is called at the end of: > org-table-expand-lhs-ranges > But at the beginning of this function the cond condition > (string-match "^@-?[-+I0-9]+\\$-?[0-9]+$" lhs) > already filteres out this case. The field descriptor is not regarded as a > range > but as a fixed field. > I changed > (string-match "^@-?[-+I0-9]+\\$-?[0-9]+$" lhs) > into > (string-match "^@-?[-+0-9]+\\$-?[0-9]+$" lhs) > without the I in the first character set. This seems to fix the bug. But I am > not sure about the side effects.
On the other hand (referring to my message in this thread just a few minutes ago) this analysis here is correct and making the change Tobias is proposing probably would work without side effects. So I step back from my earlier post and I applied the change Tobias was proposing. - Carsten
