search

GwynethLlewelyn / Go.novaextension

A quick & dirty Go language template for the Panic Nova editor
Other
34 stars 8 forks source link

Ranges of edits cannot be applied #11

Closed wtfcxt closed 3 years ago

wtfcxt commented 3 years ago

Sometimes when I try to tab (for example fmt.Println) Nova shows me this error:

Ranges of edits cannot be applied to document "<path-to-go-file>", as they exceed the current content.

I censored the path but it would show the path of the file. Any ideas why this is happening? Also I noticed that sometimes the IntelliSense doesn't work at all and the only thing it suggests is fmt.Fprint (only tested fmt for now)

GwynethLlewelyn commented 3 years ago

Interesting... I have not encountered that error before!... then again, I might not have been actively searching for it...

I've come across a few issues with IntelliSense myself, but not what you describe. I have to take a deeper look at this

wtfcxt commented 3 years ago

It seems to be quite random, sometimes it works fine and sometimes it doesn't.

GwynethLlewelyn commented 3 years ago

Eek. I hate those kinds of bugs! They're the trickiest to figure out...

jfieber commented 3 years ago

That sure sounds like a case of Nova and gopls having divergent understandings of what is in the editor. If you encounter that, does closing the file (but not the workspace window) and re-opening it sort things out?

wtfcxt commented 3 years ago

it doesn't always work

That sure sounds like a case of Nova and gopls having divergent understandings of what is in the editor. If you encounter that, does closing the file (but not the workspace window) and re-opening it sort things out?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GwynethLlewelyn/Go.novaextension/issues/11#issuecomment-827976571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM2X3F2TWPWSI24GUVMP5A3TK43B7ANCNFSM43NM7DVA .

GwynethLlewelyn commented 3 years ago

Just for the record... since Nova 7.2 (at least, possibly as early as 7.0), I have never encountered these errors again. There was a lot of refactoring done by Logan to better support LSP. At least as far as I'm concerned, it has fixed all the issues I used to have (including this one). @wtfcxt are you still having this issue? If not, can we close it?

wtfcxt commented 3 years ago

that's great! yeah we can close this issue