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

From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [patch] more Beamer properties
Date: Thu, 22 Sep 2016 10:42:16 +0200	[thread overview]
Message-ID: <878tuks4uv.fsf@gmx.us> (raw)
In-Reply-To: 87zin1j7vd.fsf@nicolasgoaziou.fr

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

>>> I think
>>>
>>>   #+TITLEGRAPHICS: [[file:link.pdf]]
>>>
>>> would be cleaner.
>>
>> I dropped this.  One might need to add attributes to the graphic.  The
>> #+titlegraphics approach wouldn’t allow it.
>
> Well, wouldn't the following work?
>
>   #+attr_beamer: :attribute1 value1 :attribute2 value2
>
>   #+TITLEGRAPHICS: [[file:link.pdf]]
>
>> +    (:beamer-short-title "SHORT_TITLE" nil nil parse)
>> +    (:beamer-short-subtitle "SHORT_SUBTITLE" nil nil parse)
>> +    (:beamer-short-author "SHORT_AUTHOR" nil nil parse)
>> +    (:beamer-short-date "SHORT_DATE" nil nil parse)
>> +    (:beamer-institute "INSTITUTE" nil nil parse)
>> +    (:beamer-short-institute "SHORT_INSTITUTE" nil nil parse)
>
> Per above, would the following be cleaner?
>
>   #+attr_beamer: :short shortdate
>
>   #+date: longdate
>
> Ditto for title, institute, author...

Looks good, but how do I get the element representation of a parsed
keyword in the :options-alist?

In the buffer, I can do

   (org-export-read-attribute :attr_beamer (org-element-at-point))

But this does not work with what is stored in the info list.

I’m probably missing something obvious here...

Thanks,
Rasmus

-- 
History is what should never happen again

next prev parent reply	other threads:[~2016-09-22  8:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30  8:38 Some LaTeX Beamer / org-mode questions Florian Lindner
2016-05-30  9:06 ` Rainer M Krug
2016-05-30  9:19 ` Rasmus
2016-05-30 11:33   ` Florian Lindner
2016-05-30 11:53     ` Rasmus
2016-06-01  8:44       ` Florian Lindner
2016-06-01 10:26         ` Rasmus
2016-06-02  8:37           ` Florian Lindner
2016-06-02  9:49             ` Rasmus
2016-06-14 12:43               ` Nicolas Goaziou
2016-09-21 11:21                 ` [patch] more Beamer properties Rasmus
2016-09-21 20:49                   ` Nicolas Goaziou
2016-09-22  8:42                     ` Rasmus [this message]
2016-09-22 22:51                       ` 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=878tuks4uv.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

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