aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAshkan Kiani <ashkan.k.kiani@gmail.com>2019-10-17 20:00:30 -0700
committerAshkan Kiani <ashkan.k.kiani@gmail.com>2019-10-17 20:00:30 -0700
commitcfb6bfa4a1a9439d98a0fa2a6b918f8168c982f9 (patch)
tree6a025a9ba97b03942ba3d515a039e2669807db8c
parentAdd Demo.gif (diff)
parentUpdate README.md (diff)
Merge branch 'master' of github.com:norcalli/nvim-colorizer.lua
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index b99acf3..3304195 100644
--- a/README.md
+++ b/README.md
@@ -26,7 +26,9 @@ lua require'colorizer'.setup()
### Why another highlighter?
-This has no external dependencies, which means you install it and it works. Other colorizers typically were synchronous and slow, as well. Being written with performance in mind and leveraging the excellent LuaJIT and a handwritten parser, updates can be done in real time. There are plugins such as [hexokinase](https://github.com/RRethy/vim-hexokinase) which have good performance, but it has some difficulty with becoming out of sync. The downside is that *this only works for Neovim*, and that will never change.
+Mostly, **RAW SPEED**.
+
+This has no external dependencies, which means you install it and **it just works**. Other colorizers typically were synchronous and slow, as well. Being written with performance in mind and leveraging the excellent LuaJIT and a handwritten parser, updates can be done in real time. There are plugins such as [hexokinase](https://github.com/RRethy/vim-hexokinase) which have good performance, but it has some difficulty with becoming out of sync. The downside is that *this only works for Neovim*, and that will never change.
Additionally, having a Lua API that's available means users can use this as a library to do custom highlighting themselves.