>>>
>>> The question is now why is this function org-babel-mark-file-as-tangled
>>> receives NULL as a buffer-file-name?
>>
>> I'm not sure, but perhaps you could wrap the body of buffer-file-name in
>> a (when (buffer-file-name) ...) form to protect against null files.
>
> Sounds reasonable and I
Eric Schulte writes:
> Rainer M Krug writes:
>
>> OK - narrowed it down to a post tangle hook which I need for proper
>> debugging of R (jumping to source line in org file and not tangled R file):
>>
>> ,
>> | #+begin_src emacs-lisp
>> | (defvar org-babel-tangled-file nil
>> | "If non-nill
Rainer M Krug writes:
> OK - narrowed it down to a post tangle hook which I need for proper
> debugging of R (jumping to source line in org file and not tangled R file):
>
> ,
> | #+begin_src emacs-lisp
> | (defvar org-babel-tangled-file nil
> | "If non-nill, current file was tangled with o
OK - narrowed it down to a post tangle hook which I need for proper
debugging of R (jumping to source line in org file and not tangled R file):
,
| #+begin_src emacs-lisp
| (defvar org-babel-tangled-file nil
| "If non-nill, current file was tangled with org-babel-tangle")
| (put 'org-babel-t
Forgot: tried with 8.2 stable release and with version from git - both
the same.
Rainer M Krug writes:
> Hi
>
> I have a strange error when tangling.
>
> I have a large org file with several code blocks tangling in about
> 20 R files and one bash file. Usually tangling works perfectly, but
> so
Hi
I have a strange error when tangling.
I have a large org file with several code blocks tangling in about
20 R files and one bash file. Usually tangling works perfectly, but
sometimes one code block does not tangle a code block to a file. These
are different blocks. When I change the name of th
