as of today's (20190118) org-plus-contrib, this seems fixed. Quick
check :
===
# Noweb syntax check
#+property: header-args:python :session
#+property: header-args:sage :session
#+name: A
#+begin_src sage
L.append(i)
#+end_src
#+na
Hello,
Robert Pluim writes:
> John Kitchin writes:
>
>> #+RESULTS:
>> : <<\([^
>> : ].+?[^ ]\|[^
>> : ]\)>>
>
> That regex looks malformed, and will only match strings with 1 or 3 or
> more characters between << and >>. If someone knows what itʼs supposed
> to be matching we can fix it. eg it l
John Kitchin writes:
> #+RESULTS:
> : <<\([^
> : ].+?[^ ]\|[^
> : ]\)>>
That regex looks malformed, and will only match strings with 1 or 3 or
more characters between << and >>. If someone knows what itʼs supposed
to be matching we can fix it. eg it looks like it wants to allow
<>
Is that some
I doubt it is Python specific, and I don't know why it would work in some
places and not others. For me, the two character name does not work in
elisp, but 1 or 3 does. I agree that seems buggy.
The origin of the problem is here:
#+BEGIN_SRC emacs-lisp
(list
(string-match (org-babel-noweb-wrap)
Le lundi 04 février 2019 à 08:11 -0500, John Kitchin a écrit :
> The problem may be the name is only two characters long. Try Ahh
> instead. That works for me.
Indeed. Nice catch ; how did you find this ?
Since this doesn't happen with emacs-lisp or Sage, and since nothing in
the docs I've read s
The problem may be the name is only two characters long. Try Ahh instead.
That works for me.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchi
Seen in `org-mode' version `9.2'.
Using `noweb' syntax works OK with `emacs-lisp':
┌
│ #+name: a
│ #+begin_src emacs-lisp
│ (setq L (append L (list i)))
│ #+end_src
│
│ #+name: b
│ #+begin_src emacs-lisp :noweb yes :exports both
│ ;; Lisp version
│ (setq L nil)
│ (dotimes (i 5) <>)
│
