Yesterday's Rose
LordChaos82@umbraroze Here I am still rocking nano and refusing to give it up ๐
simendsjo@umbraroze Then why use vim at all instead of emacs everywhere? I migrated from vim to emacs+evil-mode, so I kind of use both.
@simendsjo Because Emacs is the fancy big tool that can be used for serious things, and vi is the editor for quick changes to config files or whatever.
@umbraroze I run emacs as a daemon, and starting emacsclient is as fast as starting vim. I recommend trying it to see if you feel it solves the "quick edit" workflow.
unattributed ๐โ๏ธ@umbraroze Only problem I am seeing is that Neovim is allowing AI code. There's a whole issue / discussion about it on their repository...And now there are forks that were made before the AI code started being submitted.
For reference: https://github.com/neovim/neovim/issues/38186
Please remove #slopware LLM commits and disallow their inclusion ยท Issue #38186 ยท neovim/neovim
Problem LLMs produce non-copyrightable garbage due to being massive unethical plagiarism machines. There are already two commits that acknowledge polluting the neovim codebase. Expected behavior Th...
@unattributed My problem with those alternatives is that spite forks rarely work, because they're rarely fueled by people who want to actually contribute to the codebases.
...as an Emacs user, may I offer a constructive piece of advice to the vi community? Just toss both of them away! Start from the scratch, and write a new version of vi! In Rust, for nerd cred!
Jani Uusitalo...as an Emacs user, may I offer a constructive piece of advice to the vi community? Just toss both of them away! Start from the scratch, and write a new version of vi! In Rust, for nerd cred!
Absolutely gotta get that nerd cred!
My comment was mostly to point out the AI situation... I don't have an opinion on whether the forks are viable or not...
Rastal@umbraroze There's actually little to no benefit in this, unless you have an affinity for Lua.