From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Modifying the Beamer Exporter
Date: Sat, 29 Jun 2013 15:48:28 +0200 [thread overview]
Message-ID: <87zju9m3ir.fsf@pank.eu> (raw)
In-Reply-To: <87vc4ygfhy.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 28 Jun 2013 21:14:01 +0100")
>> I want to include my collaborators in the header of each org file just
>> as I would authors, that is by including a line like
>>
>> #+COLLABORATORS: Alice & Bob
>>
>> I've found some limited documentation on modifying the exporter (manual
>> section 12.3) and taken a look at ox.el, ox-latex.el, ox-beamer.el, etc.
>>
>> What I did was:
>> + Create a new backend derived from the beamer one
>> + add COLLABORATORS to its options-alist
>> + set the template (in translate-alist) to one handling collaborators
>>
>> This works, but before I continued on making other modifications (in a
>> similar vein), I wanted to check in with people with a higher level
>> understanding.
In general if it's generally useful make a patch (if feasible). . .
Could you point out exactly which function (with ref to the Beamer
manual) you're using? Searching for collaborator in the manual didn't
give me any hints. . .
> Maybe, maybe not. Difficult to say unless you give us a better idea of
> what kind of changes you plan on making.
To add to Eric's comment: Filters is a viable option and potentially
more sustainable if your code ain't submitted up stream.
It depends on the nature of your changes.
–Rasmus
--
This is the kind of tedious nonsense up with which I will not put
next prev parent reply other threads:[~2013-06-29 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 19:15 Modifying the Beamer Exporter Josiah Schwab
2013-06-28 20:14 ` Eric S Fraga
2013-06-28 20:53 ` Josiah Schwab
2013-06-29 13:48 ` Rasmus [this message]
2013-06-30 23:15 ` Josiah Schwab
2013-07-01 9:13 ` Rasmus
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=87zju9m3ir.fsf@pank.eu \
--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).