I made a plugin to do this too! https://github.com/tombh/novim-mode I'd never heard of OP's, I'm sure we can work together to share ideas.
What's wrong with mswin.vim that's shipped with every vim and neovim that you need to reinvent the wheel?
Modeless Vim
371–380 of 398 posts
Re: Modeless Vim
#372That’s a whole lot of code to not have to learn 10 keystrokes.
Unless of course the modal editor everyone is talking about has its most important key, i.e. the mode changing key, the furthest away possible from your fingers because of an historical accident and none of its users are talking about it and are smug about how easy it is so easy to learn a bunch of commands instead of mentioning the issue
You must be kidding. This thread is full of comments about remapping ESC to Caps Lock and other amenities like that.
Re: Modeless Vim
#373Earlier quoted context omitted.
Unless of course the modal editor everyone is talking about has its most important key, i.e. the mode changing key, the furthest away possible from your fingers because of an historical accident and none of its users are talking about it and are smug about how easy it is so easy to learn a bunch of commands instead of mentioning the issue
You must be kidding. This thread is full of comments about remapping ESC to Caps Lock and other amenities like that.
My top level comment started the thread where most of them are
Re: Modeless Vim
#374Earlier quoted context omitted.
> Back in my day, when we pressed Ctrl+S, the terminal froze, and that's just the way we liked it. I don't think anyone needs (or even wants) the terminal to freeze on such a common shortcut in 2024. Personally, I have reclaimed Ctrl S for word delete (usually done by Alt-d)
Super helpful for basically anything in a terminal. Stuff is going to flow by pretty quickly or at least keep bumping the terminal every couple seconds, usually when you _least_ want it to do so. Reading off whatever your program emitted while it's pushing the terminal up every half a second gets really annoying without Ctrl-S. It's probably the most used terminal shortcut after Ctrl-C for me.
That's a fine argument, but not relevant for when you're in an editor -- and modern TUI apps disable XON/XOFF for that reason.
Re: Modeless Vim
#375Earlier quoted context omitted.
Here's a TUI / terminal editor I'd like: VSCode clone. Reads the same config file JSON formats from the same locations, loads and renders the same color schemes, runs the same Extensions Host, exposes the same API to extensions (with some things like WebView, CustomEditor and such throwing NotSupported obviously), keeps up with changes in all those formats. Major visual difference would be that whatever the editor fo…
It's interesting that you refer to Stockholm syndrome about vscode in a thread about vim. Me, I first wrote programs in AMOS Basic, which was certainly not CUA either (I remember shift-backspace erased a whole line, which could be really frustrating). I've done enough learning of tiresome nowhere-else UIs... back when I played Nethack, I would of course insert a big S anytime I tried to save in another program for a…
Vim has pretty good support of the lsps and tree sitters that code does (at least for the languages I’ve used), I actually have a mirrored configuration between the two to simplify when I want to jump from one to the other. :)
Re: Modeless Vim
#376Conceptually the reasons the author give for this (syntax highlighting and other features of vim outclass other terminal-based editors) make total sense. That said there's something absolutely defiling about this. It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie. I love that it will make VIM more accessible for more people, but I hate how they do it. Kudos to the author.
"That said there is something absolutely defining about this."
Not expecting anyone to agree, but this is how I feel when using minimal shells that do not implement vi editing, e.g., set -V or set -o vi. Busybox/toybox is one example. In the aggregate, I actually do more editing on the command line than I do in vi. If the shell is permanently set to emacs-like keys and editing then I am constantly switching back and forth to "vi mode" everytime I edit a text file and return to the shell, i.e., nonstop.
Re: Modeless Vim
#377Earlier quoted context omitted.
Apparently coffee cake has no coffee in it so we really can’t believe anything anymore.
Next you are probably going to tell me black forest cake is not made in the black forest any more.
It’s only Black Forest cake if it comes from that region of Germany. Otherwise it’s known as Chocolate Cherry Conifer Cake.
Re: Modeless Vim
#378Is Micro[0] not a better, more purpose-fit solution to these issues? (Syntax highlighting quality, etc)
Prev discussed: https://news.ycombinator.com/item?id=37171294
Re: Modeless Vim
#379I made a plugin to do this too! https://github.com/tombh/novim-mode I'd never heard of OP's, I'm sure we can work together to share ideas.
What's wrong with mswin.vim that's shipped with every vim and neovim that you need to reinvent the wheel?
From the README:
> Vim itself already has support for something similar in its optional mswin.vim config file. However it still assumes the necessity of Normal Mode and such heritage as SHIFT+INSERT-style combinations. This plugin however, attempts to avoid Normal Mode unless absolutely necessary, say for interacting with the NERDTree buffer, wherein Insert Mode has no purpose.
Re: Modeless Vim
#380My usual comment on any thread touching vim, as an answer to all hypothetical comments talking about how vim never clicked : Remap the Escape key to CapsLock else you will never like vim (provided you are a normal person) It's the most important key and you should punctuate all your inserts with it. So it'd better not be the key that's the furthest away from your fingers. The reason that's the case is an historical a…
WHAT? HOW AM I GONNA TYPE MY SENTENCES THEN!?
> WHAT? HOW AM I GONNA TYPE MY SENTENCES THEN!?
goto visual mode , select region to capitalize , shift - U