From: Lawrence Mitchell <wence@gmx.li>
To: emacs-orgmode@gnu.org
Subject: Inconsistencies in email and author export
Date: Thu, 13 Jan 2011 14:48:42 +0000 [thread overview]
Message-ID: <m3mxn4j1v9.fsf@gmx.li> (raw)
The decision for when to add email and author information to an
exported document seems to be treated somewhat inconsistently
between export backends.
The intent appears to be that the global default for exporting
the author's name is controlled by org-export-author-info, and
the email by org-export-email-info. These can be overriden by
options in the file of the form author:value and email:value
respectively.
To check whether a backend should export the relevant info it
appears one should use:
(if (plist-get opt-plist :author-info)
;; we can export author info now
)
And similarly for email export. This obeys the file-local
setting first and foremost and then falls back on the default
value if no local setting is in effect.
However, most backends do not seem to stick to this. For example
org-docbook.el exports the author info unilaterally and the email
info if org-export-email-info is non-nil.
org-ascii.el exports the author info if org-export-author-info is
non-nil and email if both org-export-author-info and
org-export-email-info are non-nil.
org-latex.el exports the author info if :author-info is non-nil
in the options plist, and doesn't export the email info at all
(see my recent patch fixing this).
org-html.el uses org-export-author-info and
org-export-email-info.
It seems then that most backends do not pay attention to
file-local settings, which does feel like a bug.
Any thoughts?
Cheers,
Lawrence
--
Lawrence Mitchell <wence@gmx.li>
next reply other threads:[~2011-01-13 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 14:48 Lawrence Mitchell [this message]
2011-02-11 13:35 ` Inconsistencies in email and author export Bastien
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=m3mxn4j1v9.fsf@gmx.li \
--to=wence@gmx.li \
--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).