From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Oberbrunner Subject: Re: Something like SETUPFILE, but in .emacs? Date: Sun, 13 Feb 2011 13:57:15 -0500 Message-ID: References: <4d57fe92.0aeb640a.669a.4f21@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from [140.186.70.92] (port=33125 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Poh8I-0002FX-7u for emacs-orgmode@gnu.org; Sun, 13 Feb 2011 13:57:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Poh8H-0001Ja-Aw for emacs-orgmode@gnu.org; Sun, 13 Feb 2011 13:57:18 -0500 Received: from mail-gw0-f41.google.com ([74.125.83.41]:59489) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Poh8H-0001JS-4H for emacs-orgmode@gnu.org; Sun, 13 Feb 2011 13:57:17 -0500 Received: by gwj22 with SMTP id 22so1986863gwj.0 for ; Sun, 13 Feb 2011 10:57:16 -0800 (PST) In-Reply-To: <4d57fe92.0aeb640a.669a.4f21@mx.google.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Darlan Cavalcante Moreira Cc: emacs-orgmode@gnu.org On Sun, Feb 13, 2011 at 10:53 AM, Darlan Cavalcante Moreira 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. Maybe it's because I want to use it more like a word processor that can product odt, pdf, and html than an organizer, so I have dozens or hundreds of these? I really just want to set all the _defaults_ for those different export types somewhere globally, so both my large pile of existing org files as well as new ones all get a consistent look when exported. And if I change my "style" I'd like all my exports to adjust automatically. As an example, I *never* want to export the creator line. 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