This repository has been archived by the owner on Apr 16, 2024. It is now read-only.
Feature request: live-reload Doom on update #158
Assignees
Labels
branch: develop
For stuff regarding to development branch
good first issue
Good for newcomers
priority: medium
Medium priority stuff
scope: enhancement
New feature or request
Milestone
Comments
NTBBloodbath
added
scope: enhancement
NTBBloodbath
added a commit
that referenced
this issue
Oct 8, 2021
- Fix undefined log in `doom.modules` module (fixes ci too) BREAKING CHANGE: move `is_plugin_disabled` and `check_plugin` from `doom.core.functions` to `doom.utils`
NTBBloodbath
added a commit
that referenced
this issue
Oct 8, 2021
- Call modules functions in a protected call - Add `reload_lua_modules`, `reload_configs` and `full_reload` functions to reloader module
This was referenced Nov 10, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is an experiment and don't know if it's gonna even work but this would be really cool.
Basically, after a
:DoomUpdateDoom sends a log message telling the user to relaunch Neovim, but what if we avoid this and say "Ok, Doom was updated and now let's reload all Doom stuff" so the user has the live changes and can keep coding without interruptions.Also as a side request we could use jobs for updating so neovim will not become unusable until Doom gets updated.
The text was updated successfully, but these errors were encountered: