"Slawomir Grochowski" <slawomir.grochow...@gmail.com> writes:
> :COLUMNS: %40ITEM(item) %OMEGA-3-1000(omega 3){+}
> %MULTIVITAMIN(multivitamin){+}
> :COLUMNS: ...
> :COLUMNS: ...
> ...
> Because the code for the view is 'reading' the last :COLUMNS: definition with
> function (org-entry-get nil "COLUMNS" t).
>
> But is 'changing' the first :COLUMNS: definition with function
> (org-entry-put nil "COLUMNS" fmt).
>
> However, this is a bit of an inconsistency. This 'hack' could work
> without any problems. If the read and write behavior of property :COLUMNS:
> were
> predictable, same.
>
> Do you have any idea how to solve this problem?
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?
--
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>
