Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from vim to neovim #1

Closed
wants to merge 2 commits into from
Closed

Conversation

jnimety
Copy link
Collaborator

@jnimety jnimety commented Jan 11, 2023

Highlights:

  • 100% lua configuration
  • Replicated much, but not all, behavior from .vimrc
  • LSP server integration for ruby, html, js, ts, css, scss, and more
    (see home/.config/nvim/lua/plugins/lsp.lua)
    • Mason configured to auto install LSP servers
    • Note: some servers are configured to use local project binaries instead (via yarn or bundle)
  • Telescope and fzf for find, search, grep
  • Treesitter for context specific highlighting and indenting
  • Which-key for keymap hints
  • DAP setup for remote Ruby debugging (I run my projects in docker containers via docker compose)
  • Plugins manager lazy.nvim
    • loads most plugins on-demand based on configured triggers
    • add a new plugin configuration file to home/.config/nvim/lua/plugins/ to add new plugins

* Replicated much, but not all, behavior from .vimrc
* LSP server integration for ruby, html, js, ts, css, scss, and more
  (see home/.config/nvim/lua/plugins/lsp.lua)
  * Mason configured to auto install LSP servers
  * Note: some servers are configured to use local project binaries instead (via yarn or bundle)
* Telescope and fzf for find, search, grep
* Treesitter for context specific highlighting and indenting
* Which-key for keymap hints
* DAP setup for remote Ruby debugging (I run my projects in docker containers via docker compose)
* Plugins manager lazy.nvim
  * loads most plugins on-demand based on configured triggers
  * add a new plugin configuration file to home/.config/nvim/lua/plugins/ to add new plugins
@jnimety
Copy link
Collaborator Author

jnimety commented Jan 11, 2023

Hi all! I don't know if there is an appetite for this, but I thought I'd share just in case. If there's interest let's discuss here, otherwise please use this as inspiration for your personal dotfiles.

I hope everyone is doing well! -- J

@jnimety jnimety mentioned this pull request Jan 11, 2023
@jnimety
Copy link
Collaborator Author

jnimety commented Jan 11, 2023

closing PR (incorrect source branch) see #2

@jnimety jnimety closed this Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant