From: Ihor Radchenko <yantar92@posteo.net>
To: Slawomir Grochowski <slawomir.grochowski@gmail.com>
Cc: emacs-orgmode@gnu.org, t_leitner@gmx.at
Subject: Re: [FR] multiple column view definition
Date: Wed, 06 Mar 2024 10:53:50 +0000 [thread overview]
Message-ID: <87il1z3a2p.fsf@localhost> (raw)
In-Reply-To: <8734t4lji9.fsf@gmail.com>
Slawomir Grochowski <slawomir.grochowski@gmail.com> writes:
>> It looks like you are asking for a way to choose between multiple column
>> specs when building column view. And that you have a very specific idea
>> how to implement it. However, the details of the idea are elusive to me.
>> May you elaborate?
>
> Sure.
>
> We have two COLUMNS definition:
>
> * 2024
> :PROPERTIES:
> :COLUMNS: %ITEM(B) %TEST(B column)
> :COLUMNS: %ITEM(A) %TEST(A column)
> :END:
This is ambiguous in Org mode property syntax. You cannot specify
property multiple times like this. No wonder you are getting undefined
and unexpected behaviour.
> ...
> Or maybe someone has a better idea how to implement the functionality
> 'multiple column view definition'?
What you might do is hack `org-columns-get-format' to not default to
`org-columns-default-format', but instead ask user about the column
format to be used. For example, you can utilize
`org-property-get-allowed-values' and prompt user about the column
format to choose. Then, COLUMNS_ALL property may store multiple allowed
formats like:
* 2024
:PROPERTIES:
:COLUMNS_ALL: "%ITEM(B) %TEST(B column)"
:COLUMNS_ALL+: "%ITEM(A) %TEST(A column)"
:END:
--
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>
prev parent reply other threads:[~2024-03-06 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:50 [FR] multiple column view definition Slawomir Grochowski
2024-03-05 12:41 ` Ihor Radchenko
2024-03-05 16:40 ` Slawomir Grochowski
2024-03-06 10:53 ` Ihor Radchenko [this message]
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=87il1z3a2p.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=slawomir.grochowski@gmail.com \
--cc=t_leitner@gmx.at \
/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).