emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Re: Frame subtitles with org-e-beamer
Date: Fri, 27 Jul 2012 13:53:07 +0200	[thread overview]
Message-ID: <20120727115307.GA1375@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87ipd9zbis.fsf@gmail.com>

Hi Nicolas,

On Fri, Jul 27, 2012 at 01:30:51PM +0200, Nicolas Goaziou wrote:
> Hello,
> 
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > In the old beamer backend it was possible to provide a subtitle by
> > having a headline like this:
> >
> > * Frame title \\ frame subtitle
> >
> > In the new exporter this feature seems to be missing. Can this be
> > added?
> 
> I didn't include this "feature" because I wasn't comfortable with
> introducing a new syntax specific to one back-end only.
> 

I think that is a fair argument.

> It's just a matter of doing:
> 
> --8<---------------cut here---------------start------------->8---
> * Frame title
>   
>   #+BEAMER: \framesubtitle{subtitle}
> --8<---------------cut here---------------end--------------->8---
> 

This is how I worked around recently. This has a downside though, it
doesn't let you easily use markup in the subtitle (in my case I wanted
to use =keyword=). Of course this can be resolved by putting in by hand.

> Otherwise, headlines could support a :BEAMER_SUBTITLE: property which
> would just do that.
> 

Same goes here, but I would say the #+BEAMER: solution is better in
comparison. A subtitle is still part of the title, that means it
probably should be easily visible.

Given my above comment about visibility, one might then argue having a
#+BEAMER: line does not serve that purpose either when the headline is
folded. I'm not sure what is more important here, consistency between
backends[1] or readability/usability(?). It would be interesting to hear
what others think about this.

Hopefully I was clear.

Cheers,

Footnotes:

[1] IMO, an important reason for using org is backend agnostic markup.

-- 
Suvayu

Open source is the future. It sets us free.

      reply	other threads:[~2012-07-27 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27  1:30 Frame subtitles with org-e-beamer Suvayu Ali
2012-07-27  1:33 ` Suvayu Ali
2012-07-27 11:30 ` Nicolas Goaziou
2012-07-27 11:53   ` Suvayu Ali [this message]

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=20120727115307.GA1375@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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).