emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: Chris Gray <chrismgray@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-special-blocks.el is now part of the core
Date: Mon, 03 Jan 2011 21:09:16 +0100	[thread overview]
Message-ID: <4D222CEC.3070705@christianmoe.com> (raw)
In-Reply-To: <87sjx9eqt0.fsf@gnu.org>

Great! Special blocks is a really helpful contribution.

Yours,
Christian

On 1/3/11 8:21 PM, Bastien wrote:
> Hi all,
>
> Carsten received the completed FSF assignment of Chris Gray, author of
> org-special-blocks.el.  I just moved this contrib from contrib/lisp/
> into the core (lisp/), it will be part of the next Emacs release.
>
> Here is a summary of what org-special-blocks.el does:
>
> ;; This package generalizes the #+begin_foo and #+end_foo tokens.
>
> ;; To use, put the following in your init file:
> ;;
> ;; (require 'org-special-blocks)
>
> ;; The tokens #+begin_center, #+begin_verse, etc. existed previously.
> ;; This package generalizes them (at least for the LaTeX and html
> ;; exporters).  When a #+begin_foo token is encountered by the LaTeX
> ;; exporter, it is expanded into \begin{foo}.  The text inside the
> ;; environment is not protected, as text inside environments generally
> ;; is.  When #+begin_foo is encountered by the html exporter, a div
> ;; with class foo is inserted into the HTML file.  It is up to the
> ;; user to add this class to his or her stylesheet if this div is to
> ;; mean anything.
>
> Thanks Chris!
>

      reply	other threads:[~2011-01-03 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 19:21 org-special-blocks.el is now part of the core Bastien
2011-01-03 20:09 ` Christian Moe [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=4D222CEC.3070705@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=chrismgray@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).