Re: strange behaviour with $PROP_r1 value in a table

[Ihor Radchenko]

Rens Oliemans <hallo@rensoliemans.nl> writes:

> Confirmed, this is indeed strange behaviour, I think a bug.
> ...
> It seems like a mistake to convert such a cell reference in the '$PROP_x' 
> case. The
> conversion is done by 'org-table-convert-refs-to-rc', which is done before
> 'org-table-formula-substitute-names' is called. Simply changing the order 
> will not work,
> since the property value might also be a letter/number-like reference.

I just tried

#+property: r1 0.96

| value | 0.96 |
#+TBLFM: @1$2=$PROP_r1

followed by C-c C-c on TBLFM line, and I cannot reproduce.

I _can_ reproduce via C-c = -> 
`org-table-formula-from-user'/`org-table-formula-to-user'
where is it a result of the default value of `org-table-use-standard-references'

> -    (while (string-match 
> "\\<\\([a-zA-Z]+\\)\\([0-9]+\\>\\|&\\)\\|\\(;[^\r\n:]+\\|\\<remote([^,)]*)\\)"
>  s start)
> +    (while (string-match 
> "\\(\\$PROP_\\)\\{0\\}\\<\\([a-zA-Z]+\\)\\([0-9]+\\>\\|&\\)\\|\\(;[^\r\n:]+\\|\\<remote([^,)]*)\\)"
>  s start)

This is doing much more than fixing the reported bug and might affect
valid uses. I'd rather fix the bug (if it is a bug) explicitly, without
risking breaking other things.

> I have two questions about it:
>
> - The function '$PROP_<remote' still gives '#ERROR', is this related to this 
> bug, or is
>   the property name '<remote' invalid in any way and is this intended?
>
> - Should I add tests for this behaviour?

Before discussing any further, may you please check if 

#+property: r1 0.96

| value | 0.96 |
#+TBLFM: @1$2=$PROP_r1

works on your side?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>