[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Bug: code blocks with multiple word names create single word res
From: |
Nicolas Goaziou |
Subject: |
Re: [O] 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 15:05:42 +0100 |
Hello,
Joost Helberg <address@hidden> writes:
> 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?
Applied. Thank you.
Regards,
--
Nicolas Goaziou