5
30
Fork
You've already forked nvim-dev-container
3

Venvs and DAPs #94

Open
opened 2023年09月04日 19:45:50 +02:00 by GeraldIr · 1 comment

When I'm working on a project that has a poetry venv inside of a devcontainer, how can I hook up everything so that my DAP and my LSP are actually using the given virtual environment.

Am I misunderstanding what this plugin does, does it connect to the running devcontainer in the same way that VSCode does, or does this just help porting in the current neovim configuration inside of the docker container?

When I'm working on a project that has a poetry venv inside of a devcontainer, how can I hook up everything so that my DAP and my LSP are actually using the given virtual environment. Am I misunderstanding what this plugin does, does it connect to the running devcontainer in the same way that VSCode does, or does this just help porting in the current neovim configuration inside of the docker container?

Hi, thank you for checking the plugin out.

The goal is to get as close to VSCode as possible, but the plugin is not there right now. It can connect to the container in the same way by running a neovim instance in the container. When it comes to DAP and LSP, these will only work when using DevcontainerAttach (by running neovim instance in the container). Regarding that poetry venv thing, I assume you would have to activate that environment first. In that case, you could run DevcontainerAttach sh and then manually activate the venv before opening up neovim inside the container.

Hi, thank you for checking the plugin out. The goal is to get as close to VSCode as possible, but the plugin is not there right now. It can connect to the container in the same way by running a neovim instance in the container. When it comes to DAP and LSP, these will only work when using `DevcontainerAttach` (by running neovim instance in the container). Regarding that poetry venv thing, I assume you would have to activate that environment first. In that case, you could run `DevcontainerAttach sh` and then manually activate the venv before opening up neovim inside the container.
Sign in to join this conversation.
No Branch/Tag specified
main
feature/netman-integration
improvement/container-api
0.2.0
0.1.1
0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
esensar/nvim-dev-container#94
Reference in a new issue
esensar/nvim-dev-container
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?