feat: Use extractor.nvim to extract color data #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Use [extractor.nvim](https://github.com/vimcolorschemes/extractor.nvim) plugin instead of custom functions in .vimrc * Migrate the whole setup to 100% nvim. * Remove any mention of lua vs. vim colorschemes. Will bring back later when I find a way to know for sure the supported editor of a colorscheme. * Improve how plugins are installed: use packpath directory insted of adding the plugin files in the runtimepath. * Update nvim version in docker build.
reobin
force-pushed
the
feat/extractor.nvim
branch
from
18c2d2a to
6724dd9
Compare
reobin
force-pushed
the
feat/extractor.nvim
branch
from
e984368 to
6ee7c0a
Compare
reobin
force-pushed
the
feat/extractor.nvim
branch
from
274a34a to
e7f8994
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Next steps:
Closes #63