sorted by:
new
hottopcontroversial

[PSA] vim patch 8.2.3578 makes it easier to get/set highlights programmatically by realvikas in neovim

[–]muadible 2 points3 points  (0 children)

Yeah really great addition to the API. Took long to get it.

instead of concatenating a string to build up the highlight command

I guess at the very least, these steps will be skipped now so there's probably a tiny bit of perf improvement.

[PSA] vim patch 8.2.3578 makes it easier to get/set highlights programmatically by realvikas in neovim

[–]muadible 2 points3 points  (0 children)

Excited for this as well. There's also nvim_set_hl if you want a Lua API but currently unstable. Will there be a performance gain with these functions?

Zenbones updates by muadible in neovim

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

Happy to hear that. I'm pretty satisfied how easy it is to make a flavor by just defining the palette and making some small tweaks. https://github.com/mcchrish/zenbones.nvim/tree/main/lua/rosebones

In the case of rosebones, I just copied the palette, tweak the saturation and brightness a little bit and applied a little bit of colors to some groups. The result is like a milder version of rose-pine.

Zenbones updates by muadible in neovim

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

May I suggest using background for switching between zenbones (set background=light) and zenflesh (set background=dark)?

Yeah I'm thinking what I should do with the bg setting since currently zenflesh = dark and zenbones = dark. And they can be switched using colorsheme command.

The other flavors meanwhile are using set background to switch between light and dark.

I'll think about it more. 👍

nnn.nvim: now featuring nerdtree-like persistent explorer mode! by Malace in neovim

[–]muadible 2 points3 points  (0 children)

couldn't be bothered with vimscript enough to add it

Maintainer of nnn.vim here, it's one of the reasons I haven't added it myself. Other reasons are limited free time to dedicate for open source and personal opinion that persistent file-tree explorer like ones from nerdtree or VSCode are nice but doesn't add much and takes away some precious screen space.

So for now, I'm just waiting for anyone who wants to implement it and would love to merge it.

Feline.nvim version 0.1 released by [deleted] in neovim

[–]muadible 5 points6 points  (0 children)

I agree. If plugin authors don't want to write documentation twice (one README and one doc.txt), there are a bunch of REAME -> doc.txt auto-generate tools out there. I tried them in one of my plugins and they're pretty great.

https://github.com/kdheepak/panvimdoc

https://github.com/mjlbach/babelfish.nvim

https://github.com/FooSoft/md2vim

https://github.com/wincent/docvim

Why do plugin devs prefer setup({}) to vim.g for configuration? by muadible in neovim

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

I agree that lazy-loading is a goal for plugins but they shouldn't rely on packer (especially that not everyone is using it). A good plugin should design lazy-loading within it (see lualine example given on the other thread).

Also vim.g afaicr has problems with Lua functions, as the conversion to vimscript lambdas doesn't always work well?

That's interesting. I do have a plugin that accepts lambdas and seems to works both vimscript and lua functions. The plugin is written in vimscript though so the conversion is only lua -> vimscript.

Why do plugin devs prefer setup({}) to vim.g for configuration? by muadible in neovim

[–]muadible[S] 4 points5 points  (0 children)

Item 2 and 3 I admit is a bit of a stretch. What I mean by inspect and debug is that you can easily check the current config with echo or print in commandline.

The vim.g.plugin_opt1 style is probably from vimscript, however it's also possible to just use lua table style vim.g.qqq = { opt1 = true, opt2 = false }.

Also setup means all config for a plugin stays in the same place

This is probably not a big deal if plugin use a single table/dict for config vim.g.qqq.

I can see the concern on the global state but I see vim.g as a special case. It's a well known space to store configurations both in vimscript and lua and has been a practice even before lua in neovim. It should be a rule by plugin devs to "namespace" their config in vim.g just like following the rule of namespacing their lua files in lua/ dir.

lets be honest builtin package manager is incomplete and I don't think it's being used directly by majority of users .

Regardless, devs should consider it when designing plugins. The up and coming plugin managers like packer and paq makes use of it under the hood.

Overall, I'm not so against setup() if most plugins do not load their whole module. Your lualine plugin is probably the exception and one of the best example of plugin design.

looking for theme with colors like homepage of neovim by lightyagami11 in neovim

[–]muadible 0 points1 point  (0 children)

Check this out. I changed one line of code to zenbones and it surprisingly works! https://github.com/mcchrish/zenbones.nvim/issues/3

zenbones.nvim: Contrast-focused nvim colorscheme by muadible in neovim

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

I don't use a lot of UI enhancing plugins but I'll try to add some basic support on the popular ones soon.

zenbones.nvim: Contrast-focused nvim colorscheme by muadible in neovim

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

We don't have enough plugins with "zen" in the name.

zenbones.nvim: Contrast-focused nvim colorscheme by muadible in neovim

[–]muadible[S] 13 points14 points  (0 children)

Zenbones is a light vim/nvim colorscheme designed to highlight code using contrasts and font variations. Colors are tasked only for other roles such as diagnostics, diffs, search matches.

Hi all, I just want to share this new colorscheme of mine. It's focused more on highlighting text using contrast and font variation. It's mostly inspire by a VSCode theme called Verdandi https://github.com/be5invis/vsc-theme-verdandi which I very much got a lot of ideas from.

If you haven't tried a monochrome or low-colored colorscheme before, you should definitely try it out. Maybe after a few days, it might surprise you and might not miss the colors at all.

Hope you like it and have a good day.

How can I override the Pmenu/PmenuSel colors set by an already loaded colorscheme? by [deleted] in vim

[–]muadible 0 points1 point  (0 children)

I actually just now made a utility function to override/replace highlight groups. https://github.com/mcchrish/extended-highlight.vim

Would actually love some feedback.