From: Eric S Fraga <esflists@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: simplify usage of special blocks (for beamer)
Date: Sun, 02 Dec 2018 11:55:20 +0000 [thread overview]
Message-ID: <871s70xhw7.fsf@gmail.com> (raw)
In-Reply-To: <CAELgYhd3Gj5C2SMoYcW=v6j99NH2vnqxkOnctWpCNxtC1hNjBg@mail.gmail.com> (Carlos Pita's message of "Sat, 1 Dec 2018 15:41:50 -0300")
On Saturday, 1 Dec 2018 at 15:41, Carlos Pita wrote:
>> > 1. Allow for special blocks to take an :options argument.
>>
>> Although I agree that this would be nice, I imagine the difficulty
>> would be that it would be difficult to cater for multiple backends.
>
> It's not really difficult, more on the trivial side. For example, as
> an end user I already can install a filter like:
My point is that LaTeX is not the only export target for org, not that
implementing it would be difficult for a specific target. That is why
you are expected to use target specific attributes.
>> Given that beamer inherits everything that the LaTeX exporter
>> supports, is the special blocks section in the LaTeX exporter
>> documentation not already enough?
>
> Not much users seem to be aware of the ablity of using special blocks
> for beamer. No example, answer, tutorial out there even mentioned the
> possibility. Given its convenience, I would say the beamer export
> section should explicitly suggest the alternative.
I've been using special blocks in beamer from the start but there's no
harm in having an explicit mention in the beamer section of the manula,
of course. So maybe please suggest the change in the manual (i.e. post
a patch)? The manual written in org these days so easy to update.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442
prev parent reply other threads:[~2018-12-02 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 16:24 Feature request: simplify usage of special blocks (for beamer) Carlos Pita
2018-12-01 18:28 ` Eric S Fraga
2018-12-01 18:41 ` Carlos Pita
2018-12-01 19:23 ` Carlos Pita
2018-12-02 11:58 ` Eric S Fraga
2018-12-02 14:50 ` Carlos Pita
2018-12-02 15:30 ` Carlos Pita
2018-12-02 20:42 ` Nicolas Goaziou
2018-12-02 21:05 ` Carlos Pita
2018-12-02 11:55 ` Eric S Fraga [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=871s70xhw7.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=carlosjosepita@gmail.com \
--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).