emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <dandavison7@gmail.com>
To: Gary Oberbrunner <garyo@oberbrunner.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Something like SETUPFILE, but in .emacs?
Date: Sun, 13 Feb 2011 21:16:37 +0000	[thread overview]
Message-ID: <m1oc6f3aa2.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTinqH23PtN-uVfD21aUW1r=Y=DKj4Nr-C2kj1_-9@mail.gmail.com> (Gary Oberbrunner's message of "Sun, 13 Feb 2011 13:57:15 -0500")

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?

  parent reply	other threads:[~2011-02-13 21:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 21:40 Something like SETUPFILE, but in .emacs? Gary Oberbrunner
2011-02-10 21:59 ` Matthew Sauer
     [not found] ` <13311.1297374866@alphaville>
2011-02-10 22:39   ` Gary Oberbrunner
2011-02-10 23:17 ` Dan Davison
2011-02-12 12:15 ` Bastien
2011-02-13 15:53 ` Darlan Cavalcante Moreira
2011-02-13 18:57   ` Gary Oberbrunner
2011-02-13 20:40     ` Thomas S. Dye
2011-02-13 21:16     ` Dan Davison [this message]
2011-02-14  0:08       ` Bastien
2011-02-14  2:08       ` Gary Oberbrunner
2011-02-14 15:07         ` Matthew Sauer
2011-02-14 15:14           ` Matthew Sauer
2011-02-14 20:48             ` Gary Oberbrunner
     [not found]     ` <25508.1297658851@alphaville>
     [not found]       ` <AANLkTikhjWt=O6aes9P7eQWHMu5GY7_Q7Wp1omzNE__K@mail.gmail.com>
2011-02-14 20:49         ` Fwd: " Gary Oberbrunner

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=m1oc6f3aa2.fsf@gmail.com \
    --to=dandavison7@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=garyo@oberbrunner.com \
    /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).