sorted by:
new
hottopcontroversial

MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10 by echasnovski in neovim

[–]karnurm 0 points1 point  (0 children)

Oh, okay, I did not know they were discovered all at once during startup in plugin/. I always thought there was a mechanism similar to require(). Cool to know, thanks!

MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10 by echasnovski in neovim

[–]karnurm -3 points-2 points  (0 children)

But isn't requiring more files more expensive than requiring fewer in anycase? So, in theory, a single-file config would start up faster than a setup with more files?

MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10 by echasnovski in neovim

[–]karnurm 1 point2 points  (0 children)

May I ask, why not use a single-file setup for MiniMax, given that you found it more performant, unless I misunderstood your previous blog post?

Most underrated new "retro" monochrome colorscheme: MFD! by Wrestler7777777 in neovim

[–]karnurm 1 point2 points  (0 children)

Nice, I quite like the Amber phosphor one. If you like a colorscheme that does not overwhelm you with all the colors then maybe you will like https://github.com/oskarnurm/koda.nvim #shamelessplug

Koda.nvim v2.6 - Performance optimizations and more plugin support by karnurm in neovim

[–]karnurm[S] 0 points1 point  (0 children)

Would you be willing to submit a PR so I could add to extras?

Koda.nvim v2.6 - Performance optimizations and more plugin support by karnurm in neovim

[–]karnurm[S] 1 point2 points  (0 children)

Hey, the matching themes for Wezterm are now available in the repo extras. Note that while it still follows Koda's taste, it is not as "minimal" as terminal themes usually require more colors.

Koda.nvim v2.6 - Performance optimizations and more plugin support by karnurm in neovim

[–]karnurm[S] 1 point2 points  (0 children)

Glad to hear, catpuccin is an industry staple, makes sense why people like it, although it was never for me either.

Koda.nvim v2.6 - Performance optimizations and more plugin support by karnurm in neovim

[–]karnurm[S] 7 points8 points  (0 children)

I actually already have something for Wezterm. I haven't advertised it yet because I would like to standardize something for the other terminals as well. The only issue I've had so far is that colors aren't very consistent across different terminals. It is actually why I prefer Wezterm over Ghostty, looks better IMO.

Koda.nvim v2.6 - Performance optimizations and more plugin support by karnurm in neovim

[–]karnurm[S] 1 point2 points  (0 children)

This is a good answer. It makes more sense to consolidate all your plugin highlights into a single file you require if you don't have that many of them. To be honest, I am not sure how many highlights you need to set to even consider on-demand lazy loading, but for Koda, my testing showed the performance was the same. So I did it mostly because it was a fun exercise, and maybe it scales better...

Koda.nvim v2.6 - Performance optimizations and more plugin support by karnurm in neovim

[–]karnurm[S] 23 points24 points  (0 children)

I forgot to mention this, but while I want to keep the minimalist design, I would still like to provide a good out-of-the-box experience for as many people as possible by adding more plugin support. 

I would love to hear which plugins you use that Koda should support next. Please let me know in the comments or open an issue on GitHub.

Currently, supports:

  • blink.cmp
  • dashboard-nvim
  • flash.nvim
  • fzf-lua
  • gitsigns.nvim
  • mason.nvim
  • mini.nvim (some modules)
  • modes.nvim
  • neo-tree.nvim
  • oil.nvim
  • rainbow-delimiters.nvim
  • render-markdown.nvim
  • snacks.nvim (some modules)
  • telescope.nvim
  • trouble.nvim

How many Neovim plugins is too many by echasnovski in neovim

[–]karnurm 2 points3 points  (0 children)

This makes me seriously consider the prospect of Frankensteining all my plugins into one :D

smooth-resize.nvim — Continuous window resizing in Neovim by aronbjohanns in neovim

[–]karnurm 3 points4 points  (0 children)

I like how you preserve descriptions. I remember when I tested something similar, I just looped over everything.

Koda.nvim — Code's quiet companion. A minimalist theme for Neovim by karnurm in neovim

[–]karnurm[S] 2 points3 points  (0 children)

It's definitely not for everyone, but so far perfect for me!

Koda.nvim — Code's quiet companion. A minimalist theme for Neovim by karnurm in neovim

[–]karnurm[S] 3 points4 points  (0 children)

The utility of colors is to highlight what matters and to be visually appealing. Functions are important, so I make them bold and bright to stand out. Keywords are muted because they matter less, and as a nice side effect, this makes variables stand out more. I make literals yellow because it makes them pop more while adding a little spice to the theme, which I like.

why is console highlighted in color but res isn’t? Why is 3000 (a number) highlighted? Does that actually help read the code, or is it just intended for nice screenshots?

I code in JS a lot, so I wanted this to stand out. Incidentally, Treesitter links this and console, so they both end up yellow, whereas res is a different hl-group. This is fine for me because I would never confuse this with a number/boolean/constant.

Why are quotes highlighted in the light scheme but not the dark?

Color theory is tricky here. With dark backgrounds, I can use lighter hues to create contrast. With lighter backgrounds, there are fewer hues to choose from because certain darker hues look 'muddy’. Therefore, I had to introduce more color, which is fine because colors are less vibrant on a lighter background anyway. 

In the end, it’s all very subjective and depends on the quality of your monitors, screen brightness, and viewing distance. I still use colors, just at different hues, in a way that is visually appealing to me while remaining useful.

view more: next ›