From: Max Nikulin <manikulin@gmail.com>
To: Gavin Downard <gavin.downard@runbox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] lisp/org-table.el: Allow named columns on lhs
Date: Tue, 25 Jul 2023 22:01:03 +0700 [thread overview]
Message-ID: <8b17c390-4aa7-f988-aa9c-54479b8b4461@gmail.com> (raw)
In-Reply-To: <87wmyoks82.fsf@runbox.com>
On 25/07/2023 03:29, Gavin Downard wrote:
> Max Nikulin writes:
>> I have tried the patch. The formula for the named column "$three=" does
>> not work.
>>
>> | ! | one | two | three | four |
>> |---+-----+-----+-------+------|
>> | # | 1 | 2 | | 3 |
>> #+tblfm: @>$5=$one+$two::@>$three=$one+$two
>
> Yeah, I guess my current patch only supports column names in column
> formulas. Allowing column names inside of arbitrary references will take
> some more comprehensive changes. I'll see what I can do.
The regexp for parsing formulas does not allow named references after @.
I have no idea if other code should be modified as well. I consider it
as more important than detection of duplicated definitions.
A crazy idea: several columns may have the same name:
| | Jun sum | Jun count | Jun avg | Jul sum | Jul count | Jul avg |
| ! | | | average | | | average |
|---+---------+-----------+---------+---------+-----------+---------|
| | 150 | 10 | | 200 | 14 | |
#+tblfm: $average=$-2/$-1
It has no sense for numeric references but with names it can help to
avoid repeated expressions.
next prev parent reply other threads:[~2023-07-25 15:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 2:36 [PATCH] lisp/org-table.el: Allow named columns on lhs Gavin Downard
2023-07-19 7:44 ` Ihor Radchenko
2023-07-21 15:15 ` Max Nikulin
2023-07-21 18:33 ` Gavin Downard
2023-07-22 2:12 ` Max Nikulin
2023-07-22 7:25 ` Ihor Radchenko
2023-07-22 13:16 ` Max Nikulin
2023-07-22 13:25 ` Ihor Radchenko
2023-07-22 12:45 ` Max Nikulin
2023-07-22 18:21 ` Gavin Downard
2023-07-23 6:50 ` Ihor Radchenko
2023-07-24 3:25 ` Gavin Downard
2023-07-24 7:23 ` Ihor Radchenko
2023-07-24 15:17 ` Max Nikulin
2023-07-24 20:29 ` Gavin Downard
2023-07-25 15:01 ` Max Nikulin [this message]
2023-07-26 21:50 ` Gavin Downard
2023-07-27 7:36 ` Ihor Radchenko
2023-08-29 9:58 ` Ihor Radchenko
2023-08-31 14:19 ` Gavin Downard
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=8b17c390-4aa7-f988-aa9c-54479b8b4461@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gavin.downard@runbox.com \
/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).