emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Skip Collins <skip.collins@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: How to signal end of a section or subsection
Date: Wed, 22 Jan 2014 12:16:59 -0800	[thread overview]
Message-ID: <m2zjmnbwlg.fsf@polytechnique.org> (raw)
In-Reply-To: <87y5299tiy.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 21 Jan 2014 16:41:41 +0000")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I guess you can find plenty of discussions on this list on this topic so
> I won't rehash.  Just to say that there has never been a convincing use
> case that is not easily addressed with description lists and inline
> tasks.  The former can be made to look like encapsulated sections on
> export with appropriate customisation of the various export targets.
>
> I suggest you check out the list and think about your actual use case.

I have a use case for beamer export, where I have had to use latex
blocks to solve it. If I want:

,----
| blah blah
| 
| \begin{block}{Theorem}
| foo bar
| \end{block}
| 
| more blah blah
`----

I don't know how to do it using the org machinery without going back to
latex.

Alan

  reply	other threads:[~2014-01-22 20:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 15:12 How to signal end of a section or subsection Ken Mankoff
2014-01-14 16:55 ` Eric S Fraga
2014-01-15 12:24   ` Ken Mankoff
2014-01-15 17:15     ` Eric S Fraga
2014-01-20 16:30 ` Skip Collins
2014-01-21 16:41   ` Eric S Fraga
2014-01-22 20:16     ` Alan Schmitt [this message]
2014-01-22 20:22       ` Nicolas Goaziou
2014-01-22 21:38         ` Sebastien Vauban
2014-01-22 22:20           ` Nicolas Goaziou
2014-01-23  8:17             ` Sebastien Vauban
2014-01-23 11:14               ` Nicolas Goaziou
2014-01-23 22:20                 ` Sebastien Vauban
2014-01-22 21:45         ` Alan Schmitt

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=m2zjmnbwlg.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=skip.collins@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).