(Potentially) install `pyright` as the default language server

[JAS-lzn]

Pylance by nature of the agressive ToS Microsoft bakes into it, does not always work in all scenarios (eg, codium, neoVIM).

As such, it may be advantageous to use the OSS package Pyright to increase compatibility with more development ecosystems.

I believe this is standard practice in the neoVIM community although, as a degenerate VSCodium user, I can't say with any real certainty.

@HakierGrzonzo , you use neoVIM right? how do you handle python support for python?

[HakierGrzonzo]

@JAS-lzn neovim has many elaborate ways of managing LSP servers (for example pyright). I use Mason.

I do not install LSP servers per project or even system wide, neovim manages their installation and keeping them up to date.

The way most neovim users, that use m, (that being me) use m is outside of the devcontainer. Also the devcontainer.json file is VS Code specific and ignored by neovim itself.

However, this is a consideration for VS Codium users, as many linux distributions ship it instead of the official VS code binary. It will happily run devcontainer projects, but further investigation is required. It may fail to install it or Microsoft may fail to block it.

[JAS-lzn]

@JAS-lzn neovim has many elaborate ways of managing LSP servers (for example pyright). I use Mason.

I do not install LSP servers per project or even system wide, neovim manages their installation and keeping them up to date.

The way most neovim users, that use m, (that being me) use m is outside of the devcontainer. Also the devcontainer.json file is VS Code specific and ignored by neovim itself.

However, this is a consideration for VS Codium users, as many linux distributions ship it instead of the official VS code binary. It will happily run devcontainer projects, but further investigation is required. It may fail to install it or Microsoft may fail to block it.

I was thinking about in the containers, yes. Sorry, I probably should have been more specific.

For some reason, I had it in my head that neovim had some workaround for the MS devcontainer plugin, is this even true?

[HakierGrzonzo]

@JAS-lzn neovim has many elaborate ways of managing LSP servers (for example pyright). I use Mason. I do not install LSP servers per project or even system wide, neovim manages their installation and keeping them up to date. The way most neovim users, that use m, (that being me) use m is outside of the devcontainer. Also the devcontainer.json file is VS Code specific and ignored by neovim itself. However, this is a consideration for VS Codium users, as many linux distributions ship it instead of the official VS code binary. It will happily run devcontainer projects, but further investigation is required. It may fail to install it or Microsoft may fail to block it.

I was thinking about in the containers, yes. Sorry, I probably should have been more specific.

For some reason, I had it in my head that neovim had some workaround for the MS devcontainer plugin, is this even true?

There are some workarounds (no experience with this one), but they ignore the extensions configuration, since it is not applicable.