From: Joost Helberg <joost@snow.nl>
To: emacs-orgmode@gnu.org
Subject: Bug: code blocks with multiple word names create single word result-blocks leading to collisions [8.2.10 (8.2.10-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20141013/)]
Date: Wed, 18 Feb 2015 13:54:12 +0100 [thread overview]
Message-ID: <87vbizidmz.fsf@snow.nl> (raw)
hi,
noweb-syntax allows blanks in names of code blocks. The result-blocks
of these code blocks are named as well, but have everything behind the
first word stripped. This leads to result-block collisions in case
there are two code blocks starting with the same word.
Is this intentional? Why doesn't org-mode support sentences for code
block names?
It boils down to the regexp /org-babel-src-name-w-name-regexp/. It
matches a name; the match-string function is used for retrieving this
name. The regexp should obviously match the rest of the text too.
The original ob-core.el uses:
="\\([^ ()\f\t\n\r\v]+\\)"=
to match the name. Check the ' ' behind the caret.
The regexp I tested has the space removed. Hence, it will match the
full length name.
#+begin_src emacs-lisp
(setq org-babel-src-name-w-name-regexp
(concat org-babel-src-name-regexp
"\\("
org-babel-multi-line-header-regexp
"\\)*"
"\\([^()\f\t\n\r\v]+\\)"))
#+end_src
Will this just fix or also break things? Was the blank deliberately
added? If all OK, can someone please commit/push it?
Example code below:
The following snippet can be executed (C-c C-c) and included in some
script down at the bottom of this file.
#+NAME: echo the stuff
#+BEGIN_SRC sh
echo "ape nut miss"
#+END_SRC
#+RESULTS: echo the stuff
: ape nut miss
Do names with only one word still work?
#+NAME: doit
#+BEGIN_SRC sh
echo "cat boom spoil"
#+END_SRC
#+RESULTS: doit
: cat boom spoil
The next snippet will leave it's result after being executed in the
above #+RESULT: line, not the result below the code. It can be
included however in the bottom-script using noweb notation.
#+NAME: echo other stuff
#+BEGIN_SRC sh
echo "tune fire goat"
#+END_SRC
#+RESULTS: echo other stuff
: tune fire goat
We use this shell-snippet in the following script and execute it,
noweb works fine:
#+BEGIN_SRC sh :noweb yes
<<echo the stuff>>
<<echo other stuff>>
#+END_SRC
#+RESULTS:
| ape | nut | miss |
| tune | fire | goat |
many regards,
Joost
Emacs : GNU Emacs 25.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.4.2)
of 2014-10-13 on w520jo
Package: Org-mode version 8.2.10 (8.2.10-elpaplus @ /home/joost/.emacs.d/elpa/org-plus-contrib-20141013/)
--
Snow B.V.
next reply other threads:[~2015-02-18 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 12:54 Joost Helberg [this message]
2015-02-18 13:06 ` Bug: code blocks with multiple word names create single word result-blocks leading to collisions [8.2.10 (8.2.10-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20141013/)] Sebastien Vauban
2015-02-18 13:51 ` Joost Helberg
[not found] ` <87twyjiazq.fsf-JFNXyGN8thM@public.gmane.org>
2015-02-18 13:59 ` Sebastien Vauban
2015-02-18 14:05 ` Nicolas Goaziou
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=87vbizidmz.fsf@snow.nl \
--to=joost@snow.nl \
--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).