Re: Something like SETUPFILE, but in .emacs?

[Gary Oberbrunner <garyo@oberbrunner.com>]

Yes, that's definitely what I'm looking for.  If I get some time I may
write a function to allow autoloading a setupfile-syntax version (just
for consistency/simplicity), but given shortness of time I'll probably
just track down the vars and set them in my .emacs. :-)

thanks!

On Sun, Feb 13, 2011 at 4:16 PM, Dan Davison <dandavison7@gmail.com> wrote:
> Gary Oberbrunner <garyo@oberbrunner.com> writes:
>
>> On Sun, Feb 13, 2011 at 10:53 AM, Darlan Cavalcante Moreira
>> <darcamo@gmail.com> wrote:
>>> You can use auto-insert for this.
>>
>> I guess I'm really not using org-mode in the way it was intended --
>> everyone thinks I should put these values into each one of my org-mode
>> files.
>
> Hi Gary,
>
> What did you think of the suggestion I made?
>
> http://article.gmane.org/gmane.emacs.orgmode/37408
>
> I believe it pointed you in the right direction. You need to (a) find
> the variables that control the export behavior in question, and (b) set
> those variables in your .emacs. My reply gave a source of many of the
> relevant variables, i.e. the default value of the variable
> `org-export-plist-vars'. An example of one of those variables is
>
> [...]
>
>> As an example, I *never* want to export the creator line.
>
> `org-export-creator-info'.
>
> Let us know if you have trouble finding the appropriate variable for
> something, or if setting the variables isn't behaving the way you want.
>
> Dan
>
>
>>  But most of the comments on this list seem to say I should
>> modify my .org files (at least to include #+SETUPFILE), so I guess
>> I'll consider that as standard practice.
>>
>> Would anyone be interested if I were to create a way to specify export
>> values in a global file somewhere (~/.org-site-defaults or something)
>> in the same syntax as SETUPFILE (#+kwd: value) that would set up all
>> the defaults for _every_ org file?
>



-- 
-- Gary