Hendrik Tews writes:
> I believe it makes a lot of sense to have
>
> :PROPERTIES:
> :Effort: TODO
> :END:
The linter will complain about it. Effort is a special property.
> and the old behavior of treating TODO as 0 in such cases seems
> perfect to me.
>
> I believe you
Nicolas Goaziou writes:
> The intent of the check is to warn the user that a columns contains
> invalid values. Applying `string-to-number' unconditionally could give
> strange results for example, with {mean,%.2f}.
I do see your point here. I don't use mean, but it is
Hello,
Hendrik Tews writes:
> I am not sure I understand the check
>
>(when (or (not (string-match-p "[0-9]" value))
> (and (string-match-p "[1-9]" value)
> (= 0 (string-to-number value
>
> before the error message. Wouldn't
Hi,
Thanks a lot for the quick fix!
I am not sure I understand the check
(when (or (not (string-match-p "[0-9]" value))
(and (string-match-p "[1-9]" value)
(= 0 (string-to-number value
before the error message. Wouldn't it be good enough
Hello,
Hendrik Tews writes:
> in section 7.5.1.2 Column attributes, the manual says
>
> Numbers are right-aligned when a format specifier with an
> explicit width like ‘%5d’ or ‘%5.1f’ is used.
>
> However, I see something similar to
>
>5.0 | * a|
>
Hi,
in section 7.5.1.2 Column attributes, the manual says
Numbers are right-aligned when a format specifier with an
explicit width like ‘%5d’ or ‘%5.1f’ is used.
However, I see something similar to
5.0 | * a|
5.0| ** b |
when I start column view for
* a