From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Pita Subject: Feature request: simplify usage of special blocks (for beamer) Date: Sat, 1 Dec 2018 13:24:20 -0300 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40169) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gT84K-0007Ng-2R for emacs-orgmode@gnu.org; Sat, 01 Dec 2018 11:24:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gT84J-00073G-Ag for emacs-orgmode@gnu.org; Sat, 01 Dec 2018 11:24:36 -0500 Received: from mail-yb1-xb2a.google.com ([2607:f8b0:4864:20::b2a]:37784) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gT84I-00072v-3B for emacs-orgmode@gnu.org; Sat, 01 Dec 2018 11:24:35 -0500 Received: by mail-yb1-xb2a.google.com with SMTP id w129-v6so2024133ybe.4 for ; Sat, 01 Dec 2018 08:24:33 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org 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