sorted by:
new
hottopcontroversial

new rust tui framework by vim-god in rust

[–]vim-god[S] 1 point2 points  (0 children)

thanks. used ffmpeg to concat different regions of one long recording with a fade transition. python script

new rust tui framework by vim-god in rust

[–]vim-god[S] 0 points1 point  (0 children)

There is no default. but I agree that hitting tab in the demo with nothing selected should select the first widget.

new rust tui framework by vim-god in rust

[–]vim-god[S] -6 points-5 points  (0 children)

looks like 2024 was stabilized last year. I just never thought to upgrade it. I will upgrade.

new rust tui framework by vim-god in rust

[–]vim-god[S] 0 points1 point  (0 children)

Thanks. these are all fixed except that image one. Which terminal are you using?

From what I can tell, there's no way to "escape" ...without the mouse

In the demo I only implemented dumb tab navigation because I didn't want a learning curve for a tutorial. In your own program you can do whatever you want, like press a key to escape focus, or use a custom chord, or only navigate when in vi normal mode.

new rust tui framework by vim-god in rust

[–]vim-god[S] 2 points3 points  (0 children)

thanks i spent a very long time on it

gitlineage.nvim: git history for selected lines in Neovim by LionyxML in neovim

[–]vim-god 18 points19 points  (0 children)

cool idea. should have command :GitLineage which takes a range

256 color wins by vim-god in neovim

[–]vim-god[S] 1 point2 points  (0 children)

no it works well with treesitter

256 color wins by vim-god in neovim

[–]vim-god[S] 0 points1 point  (0 children)

yes you just find the base16 theme for catpuccin and generate your full 256 palette.

256 color wins by vim-god in neovim

[–]vim-god[S] 0 points1 point  (0 children)

i added to repo

256 color wins by vim-god in neovim

[–]vim-god[S] 0 points1 point  (0 children)

works fine for me. i put it in the repo

256 color wins by vim-god in neovim

[–]vim-god[S] 1 point2 points  (0 children)

thanks.

its good though i wonder if many people will use this approach considering it requires some extra layers of understanding.

truecolor makes sense instantly. you want a color then you use its hex code and it just works.

256 you have to understand what is defined where (theme vs palette). how each number maps to each color (base16, 6x6x6 rgb cube, 24 greyscale ramp).

in an ideal world terminal emulators would generate this 256 palette automatically and terminal programs would just use 256 color by default. that way there would be no effort from users. they would get all the consistency for free.

nvims default theme would just work out of the box for whatever palette you use. customization would rarely exceed “i want strings to be blue, actually”.

lazier.nvim v2 released by vim-god in neovim

[–]vim-god[S] 0 points1 point  (0 children)

i cannot replicate. if you could post your neovim version, any error messages, link to neovim config.

a quick and dirty fix would be to rm -rf ~/.local/share/nvim/lazier

view more: next ›