From: Wu Ming <wu.ming2@icloud.com>
To: emacs-orgmode@gnu.org
Subject: Re: Table column formula with remote reference
Date: Thu, 14 Mar 2024 09:16:11 +0800 [thread overview]
Message-ID: <196ADD6A-7FD8-4002-8C30-BFCFE71070BB@icloud.com> (raw)
In-Reply-To: <8734suxr7b.fsf@localhost>
> On 13 Mar 2024, at 20:16, Ihor Radchenko <yantar92@posteo.net> wrote:
>
> Wu Ming <wu.ming2@icloud.com> writes:
>
>> My fault. Missed the line "One of the very first actions during evaluation of Calc formulas and Lisp formulas is to substitute ‘@#’ and ‘$#’ in the formula with the row or column number of the field where the current result will go to.“ So '@@#' becomes '@<current row>'.
>>
>> Overlooked it also because I did read the other line "‘@0’ and ‘$0’ refer to the current row and column, respectively, i.e., to the row/column for the field being computed.” and did try '@0$1'. Why is this different from the above?
>
> See "Remote references" subsection. It explains that in
> remote(NAME,REF), REF is inside the remote table. Relative and current
> column/row is ambiguous there.
>
> In contrast, @# and $# are special - they are replaced before
> remote(...) is processed.
>
> I agree that the manual is somewhat confusing. Possibly, we may even
> change `org-table-get-remote-range' to use relative references according
> to the original table. Improvements welcome!
>
I have some trouble at understanding your answer. Do you mean @# refers a row on the table where the formula belongs and @0 refers a row on the remote table? Was tempted to describe the former as “current” but remote table is also current when accessed. A better noun may be needed.
Unrelated, but appeared on the same trial, noticed a cell was mis-calculated. Could not pin-point the reason before error disappeared after running a side formula performing the same operation. Formula was simply copying column values from a remote table. Remote table values were never changed. Recalculate all and C-c C-c were performed multiple times before the curious fix.
This made me worry about reliability of simple biz calculations I am trying on Org spreadsheet for the first time. Please advise.
Finally I moved columns but now column numbers in formulas don’t relate to column order on display. How to understand which column formula affect which column?
Sorry to coalesce multiple questions in to one. They just came to me while typing.
next prev parent reply other threads:[~2024-03-14 1:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 10:52 Table column formula with remote reference Wu Ming
2024-03-11 11:43 ` Wu Ming
2024-03-12 14:46 ` Ihor Radchenko
2024-03-13 6:04 ` Wu Ming
2024-03-13 12:16 ` Ihor Radchenko
2024-03-14 1:16 ` Wu Ming [this message]
2024-03-14 13:40 ` Fraga, Eric
2024-03-17 2:29 ` Wu Ming
2024-03-18 12:53 ` Fraga, Eric
2024-03-14 21:58 ` Ihor Radchenko
2024-03-17 2:55 ` Wu Ming
2024-03-17 14:03 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=196ADD6A-7FD8-4002-8C30-BFCFE71070BB@icloud.com \
--to=wu.ming2@icloud.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).