#+TITLE: ECM for Org-list-end-marker
#+DATE: 2011-11-24
#+PROPERTY: eval yes
* Overview
When exporting the following test case to either HTML or PDF, we get
=ORG-LIST-END-MARKER= displayed instead of the list of code blocks.
Maybe this is still not the correct way to publish a list of code blocks, but
what we get seems as well wrong to me.
* Test case
** How many blocks?
There are:
#+begin_src emacs-lisp :exports results
(org-babel-lob-ingest (buffer-file-name))
#+end_src
#+results:
: 1
blocks.
** Which blocks?
The following code is certainly not sufficient, but would aim at providing
some index to named code blocks (linkable, if possible).
#+begin_src emacs-lisp :results list
(mapcar #'list (reverse (org-babel-src-block-names)))
#+end_src
#+results:
- (#("defvar-now" 0 10 (fontified t org-category "mc-lob" face org-meta-line
font-lock-fontified t)))
** Example of block
Define date variable =now=:
#+name: defvar-now
#+begin_src sql
DECLARE @now smalldatetime
-- implementation is not important in this context!
#+end_src
Best regards,
Seb
--
Sebastien Vauban
