Do people restart Neovim or re-source init.vim when making changes to it?

• packer.nvim

  180 7,603 3.4 Lua

  A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config

I'm switching from vim-plug to packer.nvim and I noticed that they suggest to run :source init.vim/init.lua together with :PackerCompile with an autocommand whenever I save init.vim. I used to restart Neovim (or rather, open another temporary Neovim instance to test my changes) whenever I edit my configuration because I've felt like sometimes it behaves weirdly if I just re-source my init.vim, and now that I've tried it again with packer.nvim I noticed that the modifications I've done to my colorscheme dissappear.

• nvim-reload

  13 76 5.2 Lua

  Discontinued Plugin to easily reload your Neovim config

I use this plugin: https://github.com/famiu/nvim-reload

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• plenary.nvim

  58 2,368 7.5 Lua

  plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.

  

then i nil out the package.loaded (plenary.nvim has a great reload_module that also will go through all the paths in a module) and then run setup again. This way I can control how things get setup and just execute a function instead of trying to force a single require to run again. But you need to have things setup in this way so it can require the necessary files again.

• reLoad

  1 0 0.0 Lua

  Plugin to easily reload your Neovim config (by sisrfeng)

I find a solution to one of its issues. https://github.com/sisrfeng/nvim-reload/blob/master/README.md

Suggest a related project