[elpa] externals/lentic eb558ae8e3 260/333: Prepare for v0.12 release.

[ELPA Syncer]

branch: externals/lentic
commit eb558ae8e33fb532366b18e2dc33fdd1e19da6fc
Author: Phillip Lord <phillip.lord@newcastle.ac.uk>
Commit: Phillip Lord <phillip.lord@newcastle.ac.uk>

    Prepare for v0.12 release.
---
 Cask            |  2 +-
 README.md       |  9 ++++++++-
 lentic-block.el | 22 +++++++++++++++++++++-
 3 files changed, 30 insertions(+), 3 deletions(-)

diff --git a/Cask b/Cask
index 8080df17e9..f3a67c6a06 100644
--- a/Cask
+++ b/Cask
@@ -1,7 +1,7 @@
 ;; -*- emacs-lisp -*-
 (source gnu)
 (source marmalade)
-(source melpa)
+(source melpa-stable)
 
 (package-file "lentic.el")
 
diff --git a/README.md b/README.md
index be640fa2ed..8ce47d9a60 100644
--- a/README.md
+++ b/README.md
@@ -35,9 +35,16 @@ completed the relevant paperwork with the FSF.
 
 ## ChangeLog
 
+### 0.9
+
+This release introduces one new feature: unmatched-block buffers. These are
+forms of buffer where the start and end of blocks are not matched. They have
+been introduced mainly to support org-mode files which can support multiple
+embedded source languages, all of which share the same close tag.
+
 ### 0.8
 
-This buffer introduces two new features. First, it is now possible to have
+This release introduces two new features. First, it is now possible to have
 multiple lentic buffers. This is important because lentic has more than one
 use -- both for maintaining two syntactic views (for example for literate
 programming) and for maintaining two identical persistent views (for example,
diff --git a/lentic-block.el b/lentic-block.el
index f32fb2f46f..e94065b31c 100644
--- a/lentic-block.el
+++ b/lentic-block.el
@@ -55,7 +55,7 @@
 
 ;; The implementation
 
-;; ** Configuration Options
+;; ** Block Configuration
 
 ;; #+begin_src emacs-lisp
 (require 'm-buffer)
@@ -514,6 +514,26 @@ between the two buffers; we don't care which one has 
comments."
   ((conf lentic-uncommented-block-configuration))
   (oref conf :comment-stop))
 
+
+;; #+end_src
+
+;; ** Unmatched Block Configuration
+
+;; Unmatched blocks are those when the number of "start" delimitors and "end"
+;; delimitors are not the same. The motivating example here was org-mode where
+;; the =begin_src= tags name the language but the =end_src= do not. Hence, one
+;; org file with two languages break lentic.
+
+;; The solution is to search for the start tags and then take just the next 
stop
+;; tag, a solution we already use for asciidoc. The disadvantage is that the
+;; buffer can no longer become invalid which is useful for detecting 
accidentally
+;; mis-matched tags.
+
+;; The implementation is provided by the `lentic-unmatched-block-configuration'
+;; class, which is then mixed-in with the two subclasses.
+
+
+;; #+begin_src emacs-lisp
 (defclass lentic-unmatched-block-configuration ()
   ()
   :documentation "Configuration for blocked lentics where the