katawful / kat.nvim Goto Github PK

Now that I have most of my colors exported within katdotnvim.color, I think it would be best to just use those for everything instead of my current functional method

There is a massive lack in testing and assertions, this needs to be fixed

There is nothing I can do about this. A breaking version of kat.nvim must come out

This issue is about the global statusline feature recently added to NeoVim (i.e. set laststatus=3). While I prefer to keep my plugins based on NeoVim stable, I do know that this is a pretty big feature when it comes to colorschemes. If anyone is on 0.7 nightly currently and would prefer no bg color on window separators integrated into this colorscheme, let me know and I will add it into main as an option

Since I have terminal support already, having 16 color support shouldn't be too hard to add

Progress:

• 16 color theming
• kitty output
• alacritty output
• rxvt-output
• konsole output
• GTK output
• code clean up
• documentation updates

Most of this project was started before I knew much about functional programming, and thus has a lot of bad usages

Diff in particular, they need to be adapted a bit

Neovim's json integration is pretty good, I have used it in my dotfiles for exporting session data. vim.json.encode and its decode function pretty much perfectly deals with Lua tables

Currently, the exported files are fennel files built with aniseed that essentially just go through the tables I export and run them. This is really bulky, and requires a rather annoying build scheme on top of requiring fnlfmt to make the files valid before I can make them. With json, I can simply import each json as a raw table and pass it through my batch highlighting file

Depends on #16

Currently there is no way to actually interface with this colorscheme. If someone wants to add new support, say for a statusline, they basically just have to guess on how to do that. I would like to be able to give end users free access for their own uses, which would also allow simpler integration into this colorscheme as well

It can be vaguely modeled off of how I did Kreative

Encompasses the testing needed to make sure everything is ready for version 1.0

• Read through docs for grammar and clarity
• Test rendering for supported versions
• Test terminal support
• Create tags

See here: Olical/aniseed#98

Until this is fixed or a workaround is made, I am unable to even push a commit to any branch as it will immediately break Lualine, Airline, and Lightline

Currently, dynamically changing colors can be set with vim.g.kat_nvim_stupidFeatures. This was both a bad name, and poorly implemented.

Suggestions for change:

• Remove vim.g.kat_nvim_stupidFeatures
• Implement dynamicism to color table directly
• Simple function to adjust colors

Due to the breaking change found in 0.8, TS support will have to be reworked to maintain compatibility with 0.7 and 0.8 when it releases

Creating this issue now so I am aware of this when moving forward with #18

Since this scheme is dynamic, it also means its a bit slower. It'll be a lot faster with Neovim 0.7, but I would like prerendered colorscheme files eventually. Tokyonight does a similar thing

There's a fair number of missing color groups for most of the supported terminals. This issue is to address that

• kitty: https://raw.githubusercontent.com/kovidgoyal/kitty-themes/master/template.conf

• alacritty: https://github.com/alacritty/alacritty/blob/master/alacritty.yml#L188

• konsole: https://gitlab.com/jomada/moe-theme/-/blob/master/konsole/Moe.colorscheme

• urxvt: https://gist.github.com/whit/1307597/da0ef6f9aaa59b5a720e27011efe9e47e170e2b9

• render all at once instead of separate

(N)Vim reloads colorscheme on background option change.

When a color scheme is loaded (the "g:colors_name" variable is set) setting 'background' will cause the color scheme to be reloaded. If the color scheme adjusts to the value of 'background' this will work. However, if the color scheme sets 'background' itself the effect may be undone.

As such, it's sufficient to check for vim.o.background value, and select corresponding palette. This would allow one to select colorscheme kat.nvim or colorscheme kat.nwim and switch background when, for example, sun sets or rises.

Specifically, I believe this would be the core change in https://github.com/katawful/kat.nvim/blob/main/fnl/katdotnvim/main.fnl#L23 (first time dealing with LISP code, please be kind):

  (if (= vim.o.background "dark")
      (do (if (= katContrast :hard)
              (let- :g :colors_name "kat.nvim")
              (let- :g :colors_name "kat.nwim")))
      (= vim.o.background "light")
      (do (if (= katContrast :hard)
              (let- :g :colors_name "kat.lightenvim")
              (let- :g :colors_name "kat.lightenwim"))

Keyed tables in Lua do not sort, this makes unit testing very tricky. I absolutely need this for ease of developing this plugin, and need to find a way to achieve this

Currently, this theme only falls back to functional colors over JSON colors if no JSON colors are found at all. This is pretty static, and should instead check the currently desired color file to see if a JSON exists, then fallback just for that file

There's a fair bit of bad documentation throughout, as well as usage of old macros

Current all 12 foreground and background colors are predefined in a table. While this works fine for the colorscheme now, I would like to replace it with something that would generate them on the fly. This would allow me to be able to use this for a template for more themes with ease

With a minimal init.lua that just loads kat.nvim on startup, the colorscheme runs twice. This increases startup time. I do not know where the bug comes from

[Source]

underlineline -> underdouble
underdot -> underdotted
underdash -> underdashed

underdouble > undercurl wrt precedence

Hey itd be cool to have gitsigns highlights in this awesome colroscheme.

As title says, kat.nvim tag=2.0 , airline tag=v.011, airline-themes commit=cc5d3490c8f4c87d29d97df414941a9df8ceb390

vim.g.kat_nvim_dontRender and vim.g.kat_nvim_compile_enable are not needed

Also potentially deprecated vim.g.kat_nvim_commentStyle as overrides now exist

Remove all support for 0.6

Neovim 0.7 will add 2 major new features:

• Lua based user commands
• Global namespaces for highlight updates

Both will need to be added once 0.7 is out

coc.nvim

popular statuslines: (airline, galaxyline, feline, bufferline, lightline)

The pictures are outdated a bit and could use updates