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
However, integration of this configuration is still in development and not yet fully supported. Lazyman initializes Neovim configurations in headless mode and user interaction during initialization is not supported. The Vimacs configuration initialization prompts the user to accept the Cody license. This causes the Lazyman initialization process to hang and timeout.
After the timeout, Vimacs comes up cleanly so it does work in the end. I am trying to figure out how best to perform the initialization.
This is not really an issue report, more of an FYI. Your config can now be installed with Lazyman using the command:
lazyman -w Vimacs
I wanted to make it available to Lazyman users since it's pretty cool and a good NvChad example even if there is some delay in initialization. If you have any suggestions or questions or comments or concerns, please let me know.
Thanks for the good work!
The text was updated successfully, but these errors were encountered:
I've added support for installing and initializing
Vimacs
in the Lazyman Neovim Configuration Manager.However, integration of this configuration is still in development and not yet fully supported. Lazyman initializes Neovim configurations in headless mode and user interaction during initialization is not supported. The Vimacs configuration initialization prompts the user to accept the Cody license. This causes the Lazyman initialization process to hang and timeout.
After the timeout, Vimacs comes up cleanly so it does work in the end. I am trying to figure out how best to perform the initialization.
This is not really an issue report, more of an FYI. Your config can now be installed with Lazyman using the command:
I wanted to make it available to Lazyman users since it's pretty cool and a good NvChad example even if there is some delay in initialization. If you have any suggestions or questions or comments or concerns, please let me know.
Thanks for the good work!
The text was updated successfully, but these errors were encountered: