Hello,
Achim Gratz writes:
> Nicolas Goaziou writes:
>> I'm a bit surprised that was the case. When fixing the clocktable,
>> I also wondered what was the expected behaviour in that case, did some
>> quick tests and came to the conclusion empty columns were fine.
>
> I already said that I can se
Nicolas Goaziou writes:
> I'm a bit surprised that was the case. When fixing the clocktable,
> I also wondered what was the expected behaviour in that case, did some
> quick tests and came to the conclusion empty columns were fine.
I already said that I can see the utility of that in some cases, i
Hello,
Achim Gratz writes:
> So the behaviour that whatever :maxlevel is set to becomes the number of
> columns even when the rightmost columns are empty is now considered a
> feature? I haven't tried to bisect for when that changed, but empty
> columns used to be dropped from the table.
I'm a
Nicolas Goaziou writes:
> Fixed. Thank you.
So the behaviour that whatever :maxlevel is set to becomes the number of
columns even when the rightmost columns are empty is now considered a
feature? I haven't tried to bisect for when that changed, but empty
columns used to be dropped from the table.
Hello,
Stefan Nobis writes:
> In version 9.0.5 Org (Emacs 25.1) seems to generate too many columns
> in some situations. I'm not quite sure since which version this
> happens, in Org 8.x I have not seen this behaviour.
>
> Here is a small example:
>
> #+BEGIN: clocktable :maxlevel 3 :scope file
