Fixed go to definition to work with Agda 2.6+, improved unicode support, added support for python 3#52
Fixed go to definition to work with Agda 2.6+, improved unicode support, added support for python 3#521000000000 wants to merge 2 commits intoderekelkins:masterfrom
Conversation
|
Testing with Python 3.8.3, vim 8.2, and Agda 2.6.1, this did not initially work. The issue was the handling of the include paths. Changing However, there are still issues. Using this example: data ℕ : Set where
z : ℕ
s : ℕ → ℕ
foo : ℕ → ℕ
foo = λ { x → ? }if you perform a case analysis on foo = λ { z → {! !}; (s x) → {! !}which is missing the final "}", breaking the code. |
|
Thanks for the response, I'll check it out |
|
Would it be possible to just merge the "added python 3 support" commit from this PR if it's the other commit which is causing problems? NixOS recently removed python 2 support from their neovim, so I was stuck with no agda support in neovim until I discovered that I can just cherry-pick that commit to get it back (thanks @1000000000 😁) |
|
Did the changes recommended above, on https://github.com/victortaelin/agda-vim in case anyone needs it |
Go to definition
parseAnnotationImproved unicode support, added support for python 3