Possible completions are:
org-export-allow-BIND org-export-author-info
org-export-babel-evaluate org-export-blocks
org-export-blocks-postblock-hook org-export-blocks-witheld
org-export-copy-to-kill-ring org-export-creator-info
org-export-default-language org-export-email-info
org-export-exclude-tags org-export-headline-levels
org-export-highlight-first-table-line org-export-html-coding-system
org-export-html-expand org-export-html-extension
org-export-html-footnote-format org-export-html-footnotes-section
org-export-html-home/up-format org-export-html-html-helper-timestamp
org-export-html-inline-image-extensions org-export-html-inline-images
org-export-html-link-home org-export-html-link-org-files-as-html
org-export-html-link-up org-export-html-mathjax-options
org-export-html-mathjax-template org-export-html-style
org-export-html-style-extra org-export-html-style-include-default
org-export-html-style-include-scripts
org-export-html-table-align-individual-fields
org-export-html-table-tag
org-export-html-table-use-header-tags-for-first-column
org-export-html-tag-class-prefix org-export-html-title-format
org-export-html-todo-kwd-class-prefix org-export-html-toplevel-hlevel
org-export-html-use-infojs org-export-html-validation-link
org-export-html-with-timestamp org-export-html-xml-declaration
org-export-htmlize-css-font-prefix org-export-htmlize-output-type
org-export-htmlized-org-css-url org-export-interblocks
org-export-kill-product-buffer-when-displayed
org-export-language-setup org-export-latex-default-packages-alist
org-export-latex-packages-alist org-export-mark-todo-in-toc
org-export-prefer-native-exporter-for-tables
org-export-preserve-breaks org-export-remove-timestamps-from-toc
org-export-run-in-background org-export-section-number-format
org-export-select-tags org-export-show-temporary-export-buffer
org-export-skip-text-before-1st-heading org-export-table-data-tags
org-export-table-header-tags org-export-table-remove-special-lines
org-export-table-row-tags org-export-time-stamp-file
org-export-with-LaTeX-fragments org-export-with-TeX-macros
org-export-with-archived-trees org-export-with-drawers
org-export-with-emphasize org-export-with-fixed-width
org-export-with-footnotes org-export-with-priority
org-export-with-section-numbers org-export-with-special-strings
org-export-with-sub-superscripts org-export-with-tables
org-export-with-tags org-export-with-timestamps
org-export-with-toc org-export-with-todo-keywords
On Mon, Feb 14, 2011 at 9:07 AM, Matthew Sauer
<address@hidden> wrote:
Question, would something like the following work?
For .emacs
---start of .emacs ----------snip---------------snip-----------snip-------------------
(setq load-path (append '("/home/usr/emacs/load/") load-path))
(setq load-path (append '("/home/usr/emacs") load-path))
(load "export-setup" nil t ) ; Org-Export settings
<rest of .emacs code here
---end of .emacs ----------snip---------------snip-----------snip-------------------
--- Start of export-setup.el ------snip-------snip-------------snip-----------
(setq . . . . . .
. . . . . Set the variables you want here but they can be overrode in specific files with specific buffer overrides #+STARTUP
--------------end Export-setup.el
On Sun, Feb 13, 2011 at 8:08 PM, Gary Oberbrunner
<address@hidden> wrote:
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 <
address@hidden> wrote:
> Gary Oberbrunner <
address@hidden> writes:
>
>> On Sun, Feb 13, 2011 at 10:53 AM, Darlan Cavalcante Moreira
>> <
address@hidden> 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