-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agda Support #4465
Comments
I'd started on this in a branch (only stubs im afraid) #3092 I'd be happy to collaborate, but I'm also an agda novice. |
@pretentious7 thank you for doing this. Any further progress on this one ? I am unsure about how actively ASL is being developed. Is there any chance we can incorporate the Agda-mode like they have for emacs ? |
I got a bit bamboozled by the als source (and agda in general...), I'll make another go of it in a couple months. I'd like agda-mode type hole completion and stuff would be cool. |
@pretentious7 Were you ever able to get als working? I have pretty-good syntax highlighting working in #8285. I've been trying to get it to highlight function implementations to unfortunately no avail yet. The LSP has absolutely been mind-boggling though - I can't figure out what it's doing, let alone why it doesn't work - it seems to be failing to handle even basic file-was-saved events? |
Same here... I switched to emacs about a year back, though, and agda-mode is fine for me. |
Good to know 🙁 I have a sneaking suspicion that it relies on some emacs-specific implementation... |
(the function highlighting issue turned out to be a bug in tree-sitter core. still have yet to figure out als) |
I don't exactly know what editor features helix would need for a complete agda experience. I'm hoping someone more experienced with agda could help with this.
Agda has an issue for LSP support: agda/agda#3758
There is an implementation: https://github.com/banacorn/agda-language-server
It seems like helix would need
I also don't know how much should be handled by the LSP server and not helix.
Possibly relevant: microsoft/language-server-protocol#1414
The text was updated successfully, but these errors were encountered: