summaryrefslogtreecommitdiff
path: root/utils/lush-template/colors
diff options
context:
space:
mode:
authorChris <[email protected]>2021-06-30 22:03:56 -0400
committerChris <[email protected]>2021-06-30 22:03:56 -0400
commita84f5eb36b7bf742a505116483b2745e2f5414d5 (patch)
tree1bd8fb80dc7c1b95334f033b0f1469b72dc2b9f8 /utils/lush-template/colors
parent6c7717e45138e0acfc3025fa5eea8858b2cece11 (diff)
add lush and template for creating colorschemes
Diffstat (limited to 'utils/lush-template/colors')
-rw-r--r--utils/lush-template/colors/lush_template.vim21
1 files changed, 21 insertions, 0 deletions
diff --git a/utils/lush-template/colors/lush_template.vim b/utils/lush-template/colors/lush_template.vim
new file mode 100644
index 00000000..c411c149
--- /dev/null
+++ b/utils/lush-template/colors/lush_template.vim
@@ -0,0 +1,21 @@
+" You probably always want to set this in your vim file
+set background=dark
+let g:colors_name="lush_template"
+
+" By setting our module to nil, we clear lua's cache,
+" which means the require ahead will *always* occur.
+"
+" This isn't strictly required but it can be a useful trick if you are
+" incrementally editing your config a lot and want to be sure your themes
+" changes are being picked up without restarting neovim.
+"
+" Note if you're working in on your theme and have :Lushify'd the buffer,
+" your changes will be applied with our without the following line.
+"
+" The performance impact of this call can be measured in the hundreds of
+" *nanoseconds* and such could be considered "production safe".
+lua package.loaded['lush_theme.lush_template'] = nil
+
+" include our theme file and pass it to lush to apply
+lua require('lush')(require('lush_theme.lush_template'))
+