#Rust Cursive #TUI crate has a Backend trait to generalize over backends to draw with. This means any TUI backend should work. What would happen if you implemented that trait for an #OpenGL renderer... I wonder if that is what #Neovide does for #Neovim. I actually don't have any clue.

There are so many interesting resources for #rust out there, besides “the book”. I'm glad I took off all January. I will read a lot next month and tinker even more, I guess.

Especially on tutorial caught my interest. It's about creating your own editor with #rustlang.

I know there are a ton of them out there, but I want to understand how they work, not bring another one to life. I'd rather join forces and support a project I like, like #NeoVide or #wezterm.

The next year will be fun! 🥳

Trying very hard to like nvim+neovide with a doom-nvim configuration, but it's no match for Doom Emacs yet.

I like the cursor effects in neovide though.

#neovim #neovide #doomEmacs #emacs

And a companion #neovide gui wrapper for #nix that uses my whole config. Adds a mac App to the nix recipe if applicable. https://github.com/zmre/pwneovide

Did a setup of Neovim yesterday with Goneovim as the frontend and Doom-nvim as the vim configuration. This is for quick edits of files on the commandline.

This setup only works with Neovim 0.7.2.

Neovide is too buggy on macOS.

I can only remember Doom Emacs shortcuts right now. There are better configurations, but sticking to doom-nvim for muscle-memory reasons.

#neovim #textEditors #vim #doomEmacs #Goneovim #neovide

Found out about #neovide recently. A #neovim client but with some fancy cursor animations and window rendering. https://github.com/neovide/neovide

Really tempted to finally use neovim instead of my #vis and #vim combo I do now. But like those two make my life so easy. vis for all my advance text editing needs and vim for the full ide experience.