Bastien writes:
> Hi John,
>
> John J Foerch writes:
>
>> Thank you. I think of org-treat-insert-todo-heading-as-state-change as
>> part of the format of a given file, as it is analogous to 'logdone', but
>> deals with newly opened items as opposed to closed ones.
>
> There is a trade-off here:
Hi John,
John J Foerch writes:
> Thank you. I think of org-treat-insert-todo-heading-as-state-change as
> part of the format of a given file, as it is analogous to 'logdone', but
> deals with newly opened items as opposed to closed ones.
There is a trade-off here: I understand it would make s
Bastien writes:
> Hi John,
>
> John J Foerch writes:
>
>> I did not find #+STARTUP keywords for several variables that configure
>> the format of an org file:
>>
>> org-log-into-drawer
>> org-log-states-order-reversed
>
> I added logdrawer / nologdrawer and logstatesreversed / nologstatesreve
Hi John,
John J Foerch writes:
> I did not find #+STARTUP keywords for several variables that configure
> the format of an org file:
>
> org-log-into-drawer
> org-log-states-order-reversed
I added logdrawer / nologdrawer and logstatesreversed / nologstatesreversed
> org-treat-insert-todo
Hello,
I did not find #+STARTUP keywords for several variables that configure
the format of an org file:
org-log-into-drawer
org-log-states-order-reversed
org-treat-insert-todo-heading-as-state-change
I think that there should be keywords that correspond to these variables
because it would
