Nicolas Goaziou writes:
> Lele Gaifax writes:
>
>> As said, a the local COLUMNS setting is honored by the transient columns
>> view,
>> but it is ignored by org-clock-report and org-dbclock-update.
>>
>> Am I doing something wrong or isn't it possible?
>
> COLUMNS property, or keyword, are not
Hello,
Lele Gaifax writes:
> As said, a the local COLUMNS setting is honored by the transient columns view,
> but it is ignored by org-clock-report and org-dbclock-update.
>
> Am I doing something wrong or isn't it possible?
COLUMNS property, or keyword, are not related to clocktable and such.
Sorry, hit C-c C-c in the wrong buffer...
Lele Gaifax writes:
> The local property in the "Work" node is honored by org-columns (C-c C-x
> C-c),
As said, a the local COLUMNS setting is honored by the transient columns view,
but it is ignored by org-clock-report and org-dbclock-update.
Am I doi
Hi all,
I tried to use a local definition of the COLUMNS property and have a "private"
(that is, not exported to PDF) view of the time spent on something, something
like this:
# -*- coding: utf-8 -*-
#+TITLE: Test local columns
#+COLUMNS: %40ITEM(Item) %13Effort(Effort){:}
#+BEGIN: columnview :i
