Proposal V2 Updates

[erikreinert]

Overview

I want to re-write lspcontainers from scratch considering all of the challenges we have faced over the past year working on the project.

New Features

• built in TUI for ease of management of images
• build in status updates for when something is happening (image is downloading, etc)
• complete overhaul of the code to make it support multiple drivers (docker, podman, nix, etc)
• improve modularity of code for easier re-usability (right now it's mostly 1 file)
• include possible "previous versions" in TUI for backwards compatibility

[erwin]

Some feedback from a new user... Hopefully useful to you, but if not, no worries.

I've been looking at lspcontainers for a few weeks. I was using a pre-packaged neovim config (nvchad), so I had to dive into building my own ide style config before I could make sense of how I would use this. Very excited to see you're looking at doing a re-write.

For some languages, dependencies are more manageable, but for some languages, dependencies really are a train-wreck and containing them all in Docker is a massive win.

Rather than doing any of the container based config inside ~/.config/nvim I would greatly prefer something like VScode's devcontainer.json file travels along with the project... Something like EditorConfig, but for containers.

Would also be very nice to have some examples on the lspcontainers README for one line to check out a sample project and start using the LSP inside of it, for the languages that have the most need of docker managed dependencies (ruby, node and python I think). You've kind of got that with the links to the Dockerfiles, but more direct, more obvious, get going with one line in your plugin-config and then one line on the command line...

[lbene-cnx]

Hello!

I've been following this plugin as well, and I think it would be nice if the plugin could expose config or API that allows the user to rewrite the container path to the host path for the various lsp handlers that needed.

e.g. when I execute go to definition to /app/main.py then the plugin would intercept the response and navigate to /host/main.py if the mapping is /host:/app.

This would allow easy setup of the plugin even on projects where the container paths do not match the host paths