Neovim Integration has broken

In the new ide, my neovim integration has stopped working.

Both client and server side code now aren’t recognised as Python files - this seems to be because they are getting .txt appended to their names rather than .py as previously.

Any idea how we might get that back?

My current workaround is

:set filetype=python

but I have to do that every time I open a file and I’d really like to get back to not having to!

A better workaround…

The firenvim browser extension creates a temporary file whose name always begins with the domain of the site being visited. I can use that to set the filetype to python whenever it opens from anvil.works.

In my neovim config, I now have:

autocmd BufEnter anvil.works_* set filetype=python

and it works just fine (until I open a css file, but I can live with that)!

3 Likes

Fixed:

1 Like