emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: [bug] `Org-list-end-marker' displayed in exported documents
Date: Thu, 24 Nov 2011 12:44:04 +0100	[thread overview]
Message-ID: <8039ddpwxn.fsf@somewhere.org> (raw)

#+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

                 reply	other threads:[~2011-11-24 11:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8039ddpwxn.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).