emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John J Foerch <jjfoerch@earthlink.net>
To: emacs-orgmode@gnu.org
Subject: Re: #+STARTUP keywords for several variables
Date: Mon, 24 Dec 2012 12:31:16 -0500	[thread overview]
Message-ID: <87pq1z5pcr.fsf@hecubus.retroj.net> (raw)
In-Reply-To: 878v8o1ez0.fsf@bzg.ath.cx

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

  reply	other threads:[~2012-12-24 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 19:17 #+STARTUP keywords for several variables John J Foerch
2012-12-23 17:54 ` Bastien
2012-12-24 17:31   ` John J Foerch [this message]
2012-12-25  3:18     ` Bastien
2012-12-25  3:29       ` John J Foerch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pq1z5pcr.fsf@hecubus.retroj.net \
    --to=jjfoerch@earthlink.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).