From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: org-special-blocks.el is now part of the core Date: Mon, 03 Jan 2011 21:09:16 +0100 Message-ID: <4D222CEC.3070705@christianmoe.com> References: <87sjx9eqt0.fsf@gnu.org> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=37154 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PZqgp-0006pb-OZ for emacs-orgmode@gnu.org; Mon, 03 Jan 2011 15:07:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PZqgQ-00020Z-Sc for emacs-orgmode@gnu.org; Mon, 03 Jan 2011 15:07:11 -0500 Received: from mars.hitrost.net ([91.185.211.18]:39531) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PZqgQ-0001yj-N9 for emacs-orgmode@gnu.org; Mon, 03 Jan 2011 15:07:10 -0500 In-Reply-To: <87sjx9eqt0.fsf@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Chris Gray , emacs-orgmode@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! >