Daniel Hahler
Daniel Hahler
@davidhalter Yes, a simple context API would be very useful I think. It worked quite well already, until I got side-tracked by all the improvements to the tests etc.. ;)...
Not sure either. We should maybe consider to hook into the existing vim-echodoc framework? It only supports the cmdline though, and is maybe not even async itself by now -...
I think https://github.com/davidhalter/jedi-vim/pull/652 addresses this.
Just noticed that https://github.com/davidhalter/jedi-vim/pull/420 is also from me, but older - it might be obsolete, or only some parts would be still relevant.
@morphheus If you are still willing to help here, please try/review #652 first I would say.
Tests are failing, because the behavior changed. Before adjusting them, I'd like to get feedback on this.
Sure. Rebased it on master, and fixed a bug where it would not jump to the line in a new file.
I am re-opening the issue. There's likely something that jedi-vim could do better for this case, see http://vi.stackexchange.com/questions/3999/jedi-vim-and-vim-latex-buffers-problems#comment5775_4001 and the other comments.
> Probably the only solution is that the set conceallevel should be done in another place Yeah, that's what I'd say, too - probably in the the filetype plugin instead....
There is better support for setting up call signatures in #652, e.g. not setting `conceallevel` at all when using another mode than `1`.