support jedi:goto-definition from within dedicated src-block buffers in org-babel

[methuselah-0]

No description provided.

[immerrr]

Could you elaborate what is the problem that you are fixing here? I don't think I understand how jedi:source-dir, which AFAIR is the directory where jedi-core.el is stored, is related to org-babel.

[methuselah-0]

Yes, so jedi:source-dir is trying to find the source-directory of the file that is opened in the current-buffer, which is so that jedi can figure out where python modules are located and find definitions-at-point. So, say you have import ABC in the source, then you need to look and see if ABC.py exist in the same directory as the file you have opened in the current buffer. Now, when you open a src-block like below in a dedicated buffer using C-c '

#+BEGIN_SRC python :session full
some code
#+END_SRC

and from that new buffer run M-x eval-expression RET (buffer-file-name) you get nil back instead of the file-name of the org-file from which you opened the new buffer. So, in the special case of Org Src buffers, you need to do some extra work to provide the correct source directory.

[methuselah-0]

it should actually be just (org-src-source-buffer) without (current-buffer) as argument to it.

[immerrr]

I don't think you need to touch this variable, because it is the location of jedi's own sources. It probably wouldn't work anyway, because this is only evaluated once, when jedi itself is loaded.

[methuselah-0]

sorry, you are totally right. It all works fine without changing this one - everything is solved by fixing jedi:-buffer-file-name.

[methuselah-0]

Fixed so that jedi:source-dir is not changed.