From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [org.texi] New keywords tables
Date: Wed, 01 Apr 2015 13:53:24 +0200 [thread overview]
Message-ID: <87ego4f4jv.fsf@gmx.us> (raw)
In-Reply-To: <87iodgyki6.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 31 Mar 2015 22:33:53 +0200")
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> An example of a structure change is attached. It introduces a table
>> similar to @ref{Export settings} in the beginning of most backend
>> chapters.
>>
>> I have not (re)read it yet, but I want to make sure that we roughly agree
>> on the structure before I put more time into it. It does not touch
>> texinfo (yet) 'cause it's complicated.
>
> What is complicated? I find it quite clear. I'm biased, tho.
>
>> WDYT?
>
> Thanks. It is a good idea.
This time I read through the patches.
If there's no disagreements I would like to push the following patches.
After that I will update the doc changes of the SUBTITLE patch and push
that.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org.texi-Subsections-in-Beamer-export.patch --]
[-- Type: text/x-diff, Size: 2719 bytes --]
From b4bd95c7c0078f8c58fab3e6ed5a6a5ddee66872 Mon Sep 17 00:00:00 2001
From: Rasmus <rasmus@gmx.us>
Date: Wed, 1 Apr 2015 13:10:57 +0200
Subject: [PATCH 1/5] org.texi: Subsections in Beamer export
* org.texi (Beamer export): Add menu and change subheading to
subsection.
---
doc/org.texi | 23 +++++++++++++++++++----
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 780bf6f..222a9d9 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11005,7 +11005,17 @@ The @LaTeX{} class @emph{Beamer} allows production of high quality
presentations using @LaTeX{} and pdf processing. Org mode has special
support for turning an Org mode file or tree into a Beamer presentation.
-@subheading Beamer export commands
+@menu
+* Beamer specific export settings:: Export settings for Beamer export.
+* Beamer export commands:: How to export Beamer documents.
+* Sectioning Frames and Blocks in Beamer:: Blocks and sections in Beamer.
+* Beamer specific syntax:: Syntax specific to Beamer.
+* Editing support:: Helper functions for Org Beamer export.
+* A Beamer Example:: An complete Beamer example.
+@end menu
+
+@node Beamer export commands
+@subsection Beamer export commands
@table @kbd
@orgcmd{C-c C-e l b,org-beamer-export-to-latex}
@@ -11020,7 +11030,8 @@ Export as @LaTeX{} and then process to PDF.
Export as @LaTeX{} and then process to PDF, then open the resulting PDF file.
@end table
-@subheading Sectioning, Frames and Blocks
+@node Sectioning Frames and Blocks in Beamer
+@subsection Sectioning, Frames and Blocks in Beamer
Any tree with not-too-deep level nesting should in principle be exportable as
a Beamer presentation. Headlines fall into three categories: sectioning
@@ -11111,6 +11122,8 @@ such as the inclusion of short titles.}.
#+BEAMER_THEME: Rochester [height=20pt]
#+BEAMER_COLOR_THEME: spruce
@end example
+@node Beamer specific syntax
+@subsection Beamer specific syntax
Table of contents generated from @code{toc:t} @code{OPTION} keyword are
wrapped within a @code{frame} environment. Those generated from a @code{TOC}
@@ -11157,7 +11170,8 @@ the last one inserts optional arguments in current list environment.
- item 2
@end example
-@subheading Editing support
+@node Editing support
+@subsection Editing support
You can turn on a special minor mode @code{org-beamer-mode} for faster
editing with:
@@ -11172,7 +11186,8 @@ In @code{org-beamer-mode}, this key offers fast selection of a Beamer
environment or the @code{BEAMER_COL} property.
@end table
-@subheading An example
+@node A Beamer Example
+@subsection A Beamer example
Here is a simple example Org document that is intended for Beamer export.
--
2.3.4
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0002-org.texi-Change-beamer-example-to-example.patch --]
[-- Type: text/x-diff, Size: 972 bytes --]
From 7cbab3d413c9d0950817eac81cd54f4f798a1597 Mon Sep 17 00:00:00 2001
From: Rasmus <rasmus@gmx.us>
Date: Wed, 1 Apr 2015 13:12:20 +0200
Subject: [PATCH 2/5] org.texi: Change beamer example to @example
* org.texi (A Beamer Example): Change to @example.
---
doc/org.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 222a9d9..f8599bb 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11191,7 +11191,7 @@ environment or the @code{BEAMER_COL} property.
Here is a simple example Org document that is intended for Beamer export.
-@smallexample
+@example
#+TITLE: Example Presentation
#+AUTHOR: Carsten Dominik
#+OPTIONS: H:2 toc:t num:t
@@ -11223,7 +11223,7 @@ Here is a simple example Org document that is intended for Beamer export.
** Frame 2 (where we will not use columns)
*** Request
Please test this stuff!
-@end smallexample
+@end example
@node HTML export
@section HTML export
--
2.3.4
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #4: 0003-Manuals-Remove-DESCRIPTION-and-KEYWORDS.patch --]
[-- Type: text/x-diff, Size: 2262 bytes --]
From 8a37299acb5397e6f3e7c2693d7f1d6a312e2c97 Mon Sep 17 00:00:00 2001
From: Rasmus <rasmus@gmx.us>
Date: Wed, 1 Apr 2015 13:13:55 +0200
Subject: [PATCH 3/5] Manuals: Remove DESCRIPTION and KEYWORDS
* org.texi (Export settings)
orgguide.texi (Export options): Remove DESCRIPTION and KEYWORDS.
---
doc/org.texi | 15 ---------------
doc/orgguide.texi | 2 --
2 files changed, 17 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index f8599bb..905d80b 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10679,26 +10679,11 @@ A date or a time-stamp@footnote{The variable
@code{org-export-date-timestamp-format} defines how this time-stamp will be
exported.}.
-@item DESCRIPTION
-@cindex #+DESCRIPTION
-The document description. Back-ends handle it as they see fit (e.g., for the
-XHTML meta tag), if at all. The keyword is supported by @LaTeX{} back-ends,
-HTML back-ends, ASCII back-ends, the Texinfo back-end, and the ODT back-end. You
-can use several such keywords for long descriptions.
-
@item EMAIL
@cindex #+EMAIL
@vindex user-mail-address
The email address (@code{user-mail-address}).
-@item KEYWORDS
-@cindex #+KEYWORDS
-The keywords defining the contents of the document. Back-ends handle it as
-they see fit (e.g., for the XHTML meta tag), if at all. The keyword is
-supported by @LaTeX{} back-ends, HTML back-ends, ASCII back-ends, the Texinfo
-back-end, and the ODT back-end. You can use several such keywords if the list
-is long.
-
@item LANGUAGE
@cindex #+LANGUAGE
@vindex org-export-default-language
diff --git a/doc/orgguide.texi b/doc/orgguide.texi
index c3341b0..12d3a51 100644
--- a/doc/orgguide.texi
+++ b/doc/orgguide.texi
@@ -2350,8 +2350,6 @@ Insert template with export options, see example below.
#+AUTHOR: the author (default taken from @code{user-full-name})
#+DATE: a date, fixed, or an Org timestamp
#+EMAIL: his/her email address (default from @code{user-mail-address})
-#+DESCRIPTION: the page description, e.g.@: for the XHTML meta tag
-#+KEYWORDS: the page keywords, e.g.@: for the XHTML meta tag
#+LANGUAGE: language, e.g.@: @samp{en} (@code{org-export-default-language})
#+OPTIONS: H:2 num:t toc:t \n:nil ::t |:t ^:t f:t tex:t ...
@end smallexample
--
2.3.4
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #5: 0004-org.texi-New-export-keywords-sections.patch --]
[-- Type: text/x-diff, Size: 13866 bytes --]
From 09401fe35008ffa6a2f13fc888ccd9a7fb0fdd5c Mon Sep 17 00:00:00 2001
From: Rasmus <rasmus@gmx.us>
Date: Wed, 1 Apr 2015 13:34:27 +0200
Subject: [PATCH 4/5] org.texi: New export keywords sections
* org.texi (Beamer specific export settings)
(HTML Specific export settings)
(@LaTeX{} specific export settings)
(ODT specific export settings)
(Texinfo specific export settings): New sections.
(Beamer specific syntax): Removed some text.
---
doc/org.texi | 275 +++++++++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 250 insertions(+), 25 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 905d80b..67efe28 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10991,8 +10991,8 @@ presentations using @LaTeX{} and pdf processing. Org mode has special
support for turning an Org mode file or tree into a Beamer presentation.
@menu
-* Beamer specific export settings:: Export settings for Beamer export.
* Beamer export commands:: How to export Beamer documents.
+* Beamer specific export settings:: Export settings for Beamer export.
* Sectioning Frames and Blocks in Beamer:: Blocks and sections in Beamer.
* Beamer specific syntax:: Syntax specific to Beamer.
* Editing support:: Helper functions for Org Beamer export.
@@ -11015,6 +11015,56 @@ Export as @LaTeX{} and then process to PDF.
Export as @LaTeX{} and then process to PDF, then open the resulting PDF file.
@end table
+@node Beamer specific export settings
+@subsection Beamer specific export settings
+
+Beamer export introduces a number of keywords, similar to the general options
+settings described in @ref{Export settings}.
+
+@table @samp
+@item BEAMER_THEME
+@cindex #+BEAMER_THEME
+@vindex org-beamer-theme
+The Beamer theme (@code{org-beamer-theme}). Options can be specified via
+brackets, for example:
+@smallexample
+#+BEAMER_THEME: Rochester [height=20pt]
+@end smallexample
+
+@item BEAMER_FONT_THEME
+@cindex #+BEAMER_FONT_THEME
+The Beamer font theme.
+
+@item BEAMER_INNER_THEME
+@cindex #+BEAMER_INNER_THEME
+The Beamer inner theme.
+
+@item BEAMER_OUTER_THEME
+@cindex #+BEAMER_OUTER_THEME
+The Beamer outer theme.
+
+@item BEAMER_HEADER
+@cindex #+BEAMER_HEADER
+Arbitrary lines inserted into the preamble, just before the @samp{hyperref}
+settings.
+
+@item DESCRIPTION
+@cindex #+DESCRIPTION (Beamer)
+The document description. By default these are inserted as metadata using
+@samp{hyperref}. Document metadata can be configured via
+@code{org-latex-hyperref-template}. Description can also be typeset as part
+of the front matter via @code{org-latex-title-command}. You can use several
+@code{#+DESCRIPTION} keywords if the description is is long.
+
+@item KEYWORDS
+@cindex #+KEYWORDS (Beamer)
+The keywords defining the contents of the document. By default these are
+inserted as metadata using @samp{hyperref}. Document metadata can be
+configured via @code{org-latex-hyperref-template}. Description can also be
+typeset as part of the front matter via @code{org-latex-title-command}. You
+can use several @code{#+KEYWORDS} if the description is is long.
+@end table
+
@node Sectioning Frames and Blocks in Beamer
@subsection Sectioning, Frames and Blocks in Beamer
@@ -11082,34 +11132,13 @@ Although, it can also be explicitly created, with a special @code{columns}
value for @code{BEAMER_ENV} property (if it needs to be set up with some
specific options, for example).
-@subheading Beamer specific syntax
+@node Beamer specific syntax
+@subsection Beamer specific syntax
-Beamer back-end is an extension of @LaTeX{} back-end. As such, all @LaTeX{}
+The Beamer back-end is an extension of the @LaTeX{} back-end. As such, all @LaTeX{}
specific syntax (e.g., @samp{#+LATEX:} or @samp{#+ATTR_LATEX:}) is
recognized. See @ref{@LaTeX{} and PDF export} for more information.
-@cindex #+BEAMER_THEME
-@cindex #+BEAMER_COLOR_THEME
-@cindex #+BEAMER_FONT_THEME
-@cindex #+BEAMER_INNER_THEME
-@cindex #+BEAMER_OUTER_THEME
-Beamer export introduces a number of keywords to insert code in the
-document's header. Four control appearance of the presentation:
-@code{#+BEAMER_THEME}, @code{#+BEAMER_COLOR_THEME},
-@code{#+BEAMER_FONT_THEME}, @code{#+BEAMER_INNER_THEME} and
-@code{#+BEAMER_OUTER_THEME}. All of them accept optional arguments within
-square brackets. The last one, @code{#+BEAMER_HEADER}, is more generic and
-allows you to append any line of code in the header@footnote{Lines are
-appended at the end of the preamble, allowing for any final customization
-such as the inclusion of short titles.}.
-
-@example
-#+BEAMER_THEME: Rochester [height=20pt]
-#+BEAMER_COLOR_THEME: spruce
-@end example
-@node Beamer specific syntax
-@subsection Beamer specific syntax
-
Table of contents generated from @code{toc:t} @code{OPTION} keyword are
wrapped within a @code{frame} environment. Those generated from a @code{TOC}
keyword (@pxref{Table of contents}) are not. In that case, it is also
@@ -11220,6 +11249,7 @@ language, but with additional support for tables.
@menu
* HTML Export commands:: How to invoke HTML export
+* HTML Specific export settings:: Export settings for HTML export.
* HTML doctypes:: Org can export to various (X)HTML flavors
* HTML preamble and postamble:: How to insert a preamble and a postamble
* Quoting HTML tags:: Using direct HTML in Org mode
@@ -11232,6 +11262,7 @@ language, but with additional support for tables.
* JavaScript support:: Info and Folding in a web browser
@end menu
+
@node HTML Export commands
@subsection HTML export commands
@@ -11260,6 +11291,71 @@ Export to a temporary buffer. Do not create a file.
@c @noindent
@c creates two levels of headings and does the rest as items.
+@node HTML Specific export settings
+@subsection HTML Specific export settings
+HTML export introduces a number of keywords, similar to the general options
+settings described in @ref{Export settings}.
+
+@table @samp
+@item DESCRIPTION
+@cindex #+DESCRIPTION (HTML)
+The document description. This description is inserted as a HTML meta tag.
+You can use several such keywords if the list is long.
+
+@item HTML_DOCTYPE
+@cindex #+HTML_DOCTYPE
+@vindex org-html-doctype
+The document type, e.g. HTML5, (@code{org-html-doctype}).
+
+@item HTML_CONTAINER
+@cindex #+HTML_CONTAINER
+@vindex org-html-container-element
+The container, e.g. @samp{div}, used to wrap sections and elements
+(@code{org-html-container-element}).
+
+@item HTML_LINK_HOME
+@cindex #+HTML_LINK_HOME
+@vindex org-html-link-home
+The home link URL (@code{org-html-link-home}).
+
+@item HTML_LINK_UP
+@cindex #+HTML_LINK_UP
+@vindex org-html-link-up
+The up link URL (@code{org-html-link-up}).
+
+@item HTML_MATHJAX
+@cindex #+HTML_MATHJAX
+@vindex org-html-mathjax-options
+Options for the MathJax (@code{org-html-mathjax-options}). MathJax is used
+to typeset @LaTeX{} math in HTML documents. @ref{Math formatting in HTML
+export} contains an example.
+
+@item HTML_HEAD
+@cindex #+HTML_HEAD
+@vindex org-html-head
+Arbitrary lines appended to the end of the head of the document
+(@code{org-html-head}).
+
+@item HTML_HEAD_EXTRA
+@cindex #+HTML_HEAD_EXTRA
+@vindex org-html-head-extra
+Arbitrary lines appended to the end of the header of the document
+(@code{org-html-head-extra}).
+
+@item KEYWORDS
+@cindex #+KEYWORDS (HTML)
+The keywords defining the contents of the document. This description is
+inserted as a HTML meta tag. You can use several such keywords if the list
+is long.
+
+@item LATEX_HEADER
+@cindex #+LATEX_HEADER (HTML)
+Arbitrary lines appended to the preamble used when transcoding @LaTeX{}
+fragments to images. See @ref{Math formatting in HTML export} for details.
+@end table
+
+These keywords are treated in details in the following sections.
+
@node HTML doctypes
@subsection HTML doctypes
@vindex org-html-doctype
@@ -11756,6 +11852,7 @@ description.
@menu
* @LaTeX{} export commands:: How to export to LaTeX and PDF
+* @LaTeX{} specific export settings:: Export settings for @LaTeX{}
* Header and sectioning:: Setting up the export file structure
* Quoting @LaTeX{} code:: Incorporating literal @LaTeX{} code
* @LaTeX{} specific attributes:: Controlling @LaTeX{} output
@@ -11777,6 +11874,57 @@ Export as @LaTeX{} and then process to PDF.
Export as @LaTeX{} and then process to PDF, then open the resulting PDF file.
@end table
+@node @LaTeX{} specific export settings
+@subsection @LaTeX{} specific export settings
+The @LaTeX{} exporter introduces a number of keywords, similar to the general
+options settings described in @ref{Export settings}.
+
+@table @samp
+@item DESCRIPTION
+@cindex #+DESCRIPTION (@LaTeX{})
+The document description. By default these are inserted as metadata using
+@samp{hyperref}. Document metadata can be configured via
+@code{org-latex-hyperref-template}. Description can also be typeset as part
+of the front matter via @code{org-latex-title-command}. You can use several
+@code{#+DESCRIPTION} keywords if the description is is long.
+
+@item LATEX_CLASS
+@cindex #+LATEX_CLASS
+@vindex org-latex-default-class
+@vindex org-latex-classes
+The predefined preamble and headline level mapping to use
+(@code{org-latex-default-class}). Must be an element in
+@code{org-latex-classes}.
+
+@item LATEX_CLASS_OPTIONS
+@cindex #+LATEX_CLASS_OPTIONS
+Options given to the @LaTeX{} document class.
+
+@item LATEX_HEADER
+@cindex #+LATEX_HEADER
+@vindex org-latex-classes
+Arbitrary lines added to the preamble of the document, before the
+@samp{hyperref} settings. The location can be controlled via
+@code{org-latex-classes}.
+
+@item LATEX_HEADER_EXTRA
+@cindex #+LATEX_HEADER_EXTRA
+@vindex org-latex-classes
+Arbitrary lines added to the preamble of the document, before the
+@samp{hyperref} settings. The location can be controlled via
+@code{org-latex-classes}.
+
+@item KEYWORDS
+@cindex #+KEYWORDS (@LaTeX{})
+The keywords defining the contents of the document. By default these are
+inserted as metadata using @samp{hyperref}. Document metadata can be
+configured via @code{org-latex-hyperref-template}. Description can also be
+typeset as part of the front matter via @code{org-latex-title-command}. You
+can use several @code{#+KEYWORDS} if the description is is long.
+@end table
+
+These keywords are treated in details in the following sections.
+
@node Header and sectioning
@subsection Header and sectioning structure
@cindex @LaTeX{} class
@@ -12188,6 +12336,7 @@ are compatible with LibreOffice 3.4.
@menu
* Pre-requisites for ODT export:: What packages ODT exporter relies on
* ODT export commands:: How to invoke ODT export
+* ODT specific export settings:: Export settings for ODT
* Extending ODT export:: How to produce @samp{doc}, @samp{pdf} files
* Applying custom styles:: How to apply custom styles to the output
* Links in ODT export:: How links will be interpreted and formatted
@@ -12243,6 +12392,29 @@ file instead. @xref{x-export-to-other-formats, , Automatically exporting to
other formats}.
@end table
+@node ODT specific export settings
+@subsection ODT specific export settings
+The ODT exporter introduces a number of keywords, similar to the general
+options settings described in @ref{Export settings}.
+
+@table @samp
+@item DESCRIPTION
+@cindex #+DESCRIPTION (ODT)
+The document description. These are inserted as document metadata. You can
+use several such keywords if the list is long.
+
+@item KEYWORDS
+@cindex #+KEYWORDS (ODT)
+The keywords defining the contents of the document. These are inserted as
+document metadata. You can use several such keywords if the list is long.
+
+@item ODT_STYLES_FILE
+@cindex ODT_STYLES_FILE
+@vindex org-odt-styles-file
+The style file of the document (@code{org-odt-styles-file}). See
+@ref{Applying custom styles} for details.
+@end table
+
@node Extending ODT export
@subsection Extending ODT export
@@ -13120,6 +13292,7 @@ an Info file.
@menu
* Texinfo export commands:: How to invoke Texinfo export
+* Texinfo specific export settings:: Export settings for Texinfo
* Document preamble:: File header, title and copyright page
* Headings and sectioning structure:: Building document structure
* Indices:: Creating indices
@@ -13143,6 +13316,58 @@ Export to Texinfo and then process to an Info file@footnote{By setting
including DocBook.}.
@end table
+@node Texinfo specific export settings
+@subsection Texinfo specific export settings
+The Texinfo exporter introduces a number of keywords, similar to the general
+options settings described in @ref{Export settings}.
+
+@table @samp
+
+@item SUBTITLE
+@cindex #+SUBTITLE
+The document subtitle.
+
+@item SUBAUTHOR
+@cindex #+SUBAUTHOR
+The document subauthor.
+
+@item TEXINFO_FILENAME
+@cindex #+TEXINFO_FILENAME
+The Texinfo filename.
+
+@item TEXINFO_CLASS
+@cindex #+TEXINFO_CLASS
+@vindex org-texinfo-default-class
+The class of the document (@code{org-texinfo-default-class}). This must be a
+member of @code{org-texinfo-classes}.
+
+@item TEXINFO_HEADER
+@cindex #+TEXINFO_HEADER
+Arbitrary lines inserted at the end of the preamble.
+
+@item TEXINFO_POST_HEADER
+@cindex #+TEXINFO_POST_HEADER
+Arbitrary lines inserted at the end of the preamble.
+
+@item TEXINFO_DIR_CATEGORY
+@cindex #+TEXINFO_DIR_CATEGORY
+The directory category of the document.
+
+@item TEXINFO_DIR_TITLE
+@cindex #+TEXINFO_DIR_TITLE
+The directory title of the document.
+
+@item TEXINFO_DIR_DESC
+@cindex #+TEXINFO_DIR_DESC
+The directory description of the document.
+
+@item TEXINFO_PRINTED_TITLE
+@cindex #+TEXINFO_PRINTED_TITLE
+The printed title of the document.
+@end table
+
+These keywords are treated in details in the following sections.
+
@node Document preamble
@subsection Document preamble
--
2.3.4
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #6: 0005-org.texi-Changes-to-In-buffer-settings.patch --]
[-- Type: text/x-diff, Size: 958 bytes --]
From 1cf5123a01903eb6da20a77058b4d136e66bc049 Mon Sep 17 00:00:00 2001
From: Rasmus <rasmus@gmx.us>
Date: Wed, 1 Apr 2015 00:27:07 +0200
Subject: [PATCH 5/5] org.texi: Changes to In-buffer settings
* org.texi (In-buffer settings): Remove keywords not defined in ox.el
---
doc/org.texi | 4 ----
1 file changed, 4 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 67efe28..0342c07 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -17134,10 +17134,6 @@ multiple #+TBLFM lines} in @ref{Editing and debugging formulas}.
@item #+TITLE:, #+AUTHOR:, #+EMAIL:, #+LANGUAGE:, #+DATE:,
@itemx #+OPTIONS:, #+BIND:,
-@itemx #+DESCRIPTION:, #+KEYWORDS:,
-@itemx #+LATEX_HEADER:, #+LATEX_HEADER_EXTRA:,
-@itemx #+HTML_HEAD:, #+HTML_HEAD_EXTRA:, #+HTML_LINK_UP:, #+HTML_LINK_HOME:,
-@itemx #+ODT_STYLES_FILE:,
@itemx #+SELECT_TAGS:, #+EXCLUDE_TAGS:
These lines provide settings for exporting files. For more details see
@ref{Export settings}.
--
2.3.4
next prev parent reply other threads:[~2015-04-01 11:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 14:19 [ox, patch] #+SUBTITLE Rasmus
2015-03-27 15:08 ` Andreas Leha
2015-03-27 15:12 ` Rasmus
2015-03-27 15:35 ` Andreas Leha
2015-03-28 15:40 ` Nicolas Goaziou
2015-03-28 15:55 ` Rasmus
2015-03-28 17:15 ` Thomas S. Dye
2015-03-29 9:44 ` Nicolas Goaziou
2015-03-29 11:50 ` Rasmus
2015-03-29 13:05 ` Nicolas Goaziou
2015-03-29 13:13 ` Rasmus
2015-03-30 7:39 ` Nicolas Goaziou
2015-03-30 10:35 ` Rasmus
2015-03-31 10:18 ` Nicolas Goaziou
2015-03-31 10:35 ` Rasmus
2015-03-31 10:47 ` Nicolas Goaziou
2015-03-31 15:50 ` [org.texi] New keywords tables (was: [ox, patch] #+SUBTITLE) Rasmus
2015-03-31 20:33 ` [org.texi] New keywords tables Nicolas Goaziou
2015-03-31 21:57 ` Rasmus
2015-04-01 11:53 ` Rasmus [this message]
2015-04-01 19:37 ` Nicolas Goaziou
2015-04-01 21:55 ` Rasmus
2015-04-01 22:34 ` [ox, patch] #+SUBTITLE Rasmus
2015-04-08 21:25 ` Rasmus
2015-03-29 11:16 ` Rasmus
2015-03-31 10:21 ` Nicolas Goaziou
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=87ego4f4jv.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).