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

From: Carlos Pita <carlosjosepita@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Feature request: simplify usage of special blocks (for beamer)
Date: Sat, 1 Dec 2018 13:24:20 -0300	[thread overview]
Message-ID: <CAELgYhfc6S-dRJDVcM-53LNhQJw4hBkrOFmujCH8ODEcKVUsBw@mail.gmail.com> (raw)

Hi all!

The standard mapping from org structures to beamer structures
introduces boilerplate:

1. At the bare minimum a properties drawer.
2. Then there is the tag.
3. But above all the need to add an ignoreheading subsection (with its
drawer and everything) to introduce a little text between, say, two
definition blocks.

Now, there are special blocks [1] also, and it's a pity they are not
suggested for beamer blocks nor in the org manual nor in the org
beamer tutorial. IMO they are a better fit for simple beamer blocks.
They don't nest, so org headings still have a purpose here for complex
layouts, but they close naturally without the need of
ignoreheading-like tricks, and this covers most cases of practical
importance.

Now, that it's great but the way they take their options is more
clunky than it could be. You need to add a #+ATTR_LATEX: options:...
line above, burying the block title into syntactical noise. It would
be nice it they took their options directly instead, as src blocks do.
For example:

#+BEGIN_definition :options [I'm the definiendum]
I'm the definition
#+END_definition

So my request would be:

1. Allow for special blocks to take an :options argument.

2. Mention the possibility of using special blocks to represent beamer
blocks, be it in the manual or in the tutorial.

Best regards
--
Carlos

[1] https://orgmode.org/manual/Special-blocks-in-LaTeX-export.html

next             reply	other threads:[~2018-12-01 16:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 16:24 Carlos Pita [this message]
2018-12-01 18:28 ` Feature request: simplify usage of special blocks (for beamer) 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

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=CAELgYhfc6S-dRJDVcM-53LNhQJw4hBkrOFmujCH8ODEcKVUsBw@mail.gmail.com \
    --to=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

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