From: Giorgio Valoti <giorgio_v@me.com>
To: emacs-orgmode@gnu.org
Subject: Re: Unable to select source code blocks
Date: Sat, 26 Feb 2011 09:39:23 +0100 [thread overview]
Message-ID: <2DD6BE58-EAB5-4335-B579-B48F2D79F705@me.com> (raw)
In-Reply-To: <87r5avhb46.fsf@gmail.com>
Il giorno 26/feb/2011, alle ore 01.08, Eric Schulte ha scritto:
>>> […]
>>
>> The problem doesn’t seem related to the autocomplete system, it’s the
>> org-babel-src-block-names function that returns an empty list. I don’t
>> know why, the org-babel-src-name-w-name-regexp used by that function
>> seems ok at a cursory look.
>>
>
> Could you attach a small file with named code blocks which aren't caught
> by this function? I just ran the following in by file of scraps of
> code examples and got 60 names returned
>
> #+begin_src emacs-lisp
> (length (org-babel-src-block-names))
> #+end_src
How embarrassing! I used this
#+begin_src emacs-lisp
(org-babel-src-block-names)
#+end_src
which returns nil or so I thought. I was expecting to see the list of source blocks in the results.
Using your snippet on the same file:
#+begin_src emacs-lisp
(length (org-babel-src-block-names))
#+end_src
#+results:
: 19
However, using eval-last-sexp I get a list with nil items. Is it correct?
Ciao
--
Giorgio Valoti
next prev parent reply other threads:[~2011-02-26 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 7:11 Unable to select source code blocks Giorgio Valoti
2011-02-21 11:51 ` Eric S Fraga
2011-02-22 9:52 ` Giorgio Valoti
[not found] ` <8762sbfca5.fsf@ucl.ac.uk>
2011-02-25 17:42 ` Giorgio Valoti
2011-02-26 0:08 ` Eric Schulte
2011-02-26 8:39 ` Giorgio Valoti [this message]
2011-02-26 16:05 ` Eric Schulte
2011-02-26 21:03 ` Giorgio Valoti
2011-02-27 19:53 ` Eric Schulte
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=2DD6BE58-EAB5-4335-B579-B48F2D79F705@me.com \
--to=giorgio_v@me.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).