aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAshkan Kiani <ashkan.k.kiani@gmail.com>2019-10-17 19:49:56 -0700
committerGitHub <noreply@github.com>2019-10-17 19:49:56 -0700
commit7cf9641be21baeaf05313773d42da02a53cc9a26 (patch)
tree4d121460d557847b8c514e223681288c5c846865
parentLICENSE (diff)
Update README.md
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index 1968335..509fb9e 100644
--- a/README.md
+++ b/README.md
@@ -24,7 +24,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.