emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Josiah Schwab <jschwab@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Modifying the Beamer Exporter
Date: Sun, 30 Jun 2013 16:15:30 -0700	[thread overview]
Message-ID: <87mwq7xka5.fsf@gmail.com> (raw)
In-Reply-To: <87zju9m3ir.fsf@pank.eu>


>>> 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. . .

For my subtitle example, \subtitle{} is a beamer command so I can make
a patch for that and see what people think.

There is no beamer command for collaborators -- which is why you didn't
find it in the manual.  But I almost always have collaborators on my
presentations, so I want to choose once how to render collaborators and
then ever after only have to set the content.

That could either mean adding a custom \collaborators{} command in my
personal beamer theme and have the exporter set that appropriately or
just having my local exporter do something like

(format "\\author{%s \\\\{\\small with %s}}\n" author collaborators)

when COLLABORATORS is set.

>> 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.

Ok, I will go read more about filters in the manual and come back to
the list if I have questions.

Thanks for your time!

Best,
Josiah

next prev parent reply	other threads:[~2013-06-30 23:16 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
2013-06-30 23:15     ` Josiah Schwab [this message]
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=87mwq7xka5.fsf@gmail.com \
    --to=jschwab@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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

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).