You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that Daytona supports "ANY IDE," including popular editors like Visual Studio Code, JetBrains, and Vim. I primarily use Neovim and, like many Neovim users, rely on the LazyVim package manager to handle my plugins and configurations.
Could you clarify if Daytona fully supports Neovim, particularly with configurations managed through LazyVim? Specifically, I’d like to know:
Compatibility: Are there any limitations or adjustments required to ensure Daytona’s compatibility with LazyVim configurations?
Plugin Support: Does Daytona have any known issues with Neovim plugins (e.g., LSP integrations, treesitter) when managed by LazyVim?
Having clear information about Neovim + LazyVim compatibility would be extremely helpful for developers looking to incorporate Daytona into their workflows.
The text was updated successfully, but these errors were encountered:
Daytona does not handle syncing your Neovim config automatically. Instead, it allows you to connect to your workspaces via SSH by running daytona ssh or daytona code (you can set Terminal SSH as the default IDE when you run daytona ide).
For syncing configs, maybe you can look into Transfer.nvim as I suggested here #963 (comment).
Additionally, I believe that, when we implement dotfiles support, you could sync your configs by configuring dotfiles that will be installed in all of your workspaces.
I noticed that Daytona supports "ANY IDE," including popular editors like Visual Studio Code, JetBrains, and Vim. I primarily use Neovim and, like many Neovim users, rely on the LazyVim package manager to handle my plugins and configurations.
Could you clarify if Daytona fully supports Neovim, particularly with configurations managed through LazyVim? Specifically, I’d like to know:
Compatibility: Are there any limitations or adjustments required to ensure Daytona’s compatibility with LazyVim configurations?
Plugin Support: Does Daytona have any known issues with Neovim plugins (e.g., LSP integrations, treesitter) when managed by LazyVim?
Having clear information about Neovim + LazyVim compatibility would be extremely helpful for developers looking to incorporate Daytona into their workflows.
The text was updated successfully, but these errors were encountered: