#+STARTUP keywords for several variables

#+STARTUP keywords for several variables

[John J Foerch]

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 make it easier to share org files among different
emacses with different org configurations.  File-local variables can
currently be used to configure these variables, but #+STARTUP keywords
would be more elegant.

Thank you,

John Foerch

Re: #+STARTUP keywords for several variables

[Bastien]

Hi John,

John J Foerch <jjfoerch@earthlink.net> 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-heading-as-state-change

For this one, I think it falls into the "really-just-an-option-
and-we-cannot-have-startup-keywords-for-every-option" category :)

> I think that there should be keywords that correspond to these variables
> because it would make it easier to share org files among different
> emacses with different org configurations.  File-local variables can
> currently be used to configure these variables, but #+STARTUP keywords
> would be more elegant.

Note that you can also bind variables with #+BIND.

Thanks,

-- 
 Bastien

Re: #+STARTUP keywords for several variables

[John J Foerch]

Bastien <bzg@altern.org> writes:
> Hi John,
>
> John J Foerch <jjfoerch@earthlink.net> 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-heading-as-state-change
>
> For this one, I think it falls into the "really-just-an-option-
> and-we-cannot-have-startup-keywords-for-every-option" category :)
>
>> I think that there should be keywords that correspond to these variables
>> because it would make it easier to share org files among different
>> emacses with different org configurations.  File-local variables can
>> currently be used to configure these variables, but #+STARTUP keywords
>> would be more elegant.
>
> Note that you can also bind variables with #+BIND.
>
> Thanks,

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.  I didn't know
about #+BIND - will check it out.

Thanks again,

-- 

John Foerch

Re: #+STARTUP keywords for several variables

[Bastien]

Hi John,

John J Foerch <jjfoerch@earthlink.net> 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 sense from your
problem's point of vue (sharing files and config easily) but I don't
want to add to many #+STARTUP keywords, there are already too many to
my taste.  If you can use #+BIND for this, it's better IMHO.

-- 
 Bastien

Re: #+STARTUP keywords for several variables

[John J Foerch]

Bastien <bzg@altern.org> writes:
> Hi John,
>
> John J Foerch <jjfoerch@earthlink.net> 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 sense from your
> problem's point of vue (sharing files and config easily) but I don't
> want to add to many #+STARTUP keywords, there are already too many to
> my taste.  If you can use #+BIND for this, it's better IMHO.

Okay, works for me.  Thank you for your work.

-- 
John Foerch