Sandy Maguire
Sandy Maguire
I just wanted to chime in saying we're hitting this problem as well.
Weird. This is definitely a regression, but I can indeed reproduce it :confused: I'm not actively writing any Agda these days, so it might take some time to tackle this...
This is almost certainly the problem: https://github.com/isovector/cornelis/blob/06d6020eed1a3520bb2887337dd5b27b1755968b/src/Plugin.hs#L68 which a quick fix might be ```haskell let buffer_idx = toBytes contents $ incIndex $ zeroIndex $ ds_position ds ``` The vim API...
I don't think there's any way, today! I'm open to suggestions for what you'd like to happen, though.
I'm open to this! I often `setf agda` just to bring those bindings into scope :) I likely won't do any work here, but I'd be happy for a PR.
Looking through the documentation, it seems we MUST have a token to start each line in a multi line comment. > Three-piece comments must have a middle string because otherwise...
I think this will be a hard one to fix; last I checked, Agda doesn't give us the buffer range we need to change when it gives splits. If that's...
To do the extmarks stuff, we'll need a map from interaction points to their extmarks. And then check whether `nvim_buf_get_extmark_by_id` with the `details` option correctly gives back the ending of...
This might now be fixed by @Lysxia's new patch.
Is it possible to make a new command that provides the synchronous behavior? That would be preferable in my book. If so, I'd be willing to merge such a change.