151–160 of 398 posts
Earlier quoted context omitted.
Good to know. Of course, I did have to google how to quit easy vim.
> I did have to google how to quit easy vim. For those who know how to quit vim, but want to experience "how do I quit" again, try running `:term`.
Earlier quoted context omitted.
> vi and vim have modes because they were created in an era where computing and terminal capabilities were very limited vim was released in 1991. Same year linux kernel started and Apple PowerBook came out. Limited terminal capabilities is not the reason vim is modal.
Vim was heavily based on vi, and vi was designed for limited terminal capacities.
Earlier quoted context omitted.
> vi and vim have modes becaus they were created in an era where computing and terminal capabilities were very limited. that's the whole point. it was designed for limited terminals and high latency, very slow serial links. that means when you learn it and all of its shortcuts and you have a fast and modern terminal, you are able to edit at ludicrous speed. it's like training at altitude or running with weight belts…
I just don't believe that the average vim users edits significantly faster than non vim users. I mean, maybe 5% faster. Sure. Maybe. But at what price? _At what price, I ask you??_
In Vim, I enjoy the process of text editing itself (in addition to any joy derived from the substance of the text edited).
Seems maybe author did not know that this is already built into vim?: "easy vim", aka evim, or "vim -y". see "man vim" That said, if modeless editor you are looking for... then vim is not the editor you're looking for. It goes against what vim is, and hamstrings it. Learning vim is a journey, and once comfort sets in, you will understand why, why vim.
Not the first, not the last hacky project. Saying that it goes against what it is makes me think of JS V8 being used outside of browser.
Perhaps there are good reasons for not having modeless vim (or server side js for that matter), but the industry overwhelmingly accepts good enough solutions, with good enough results.
Vim go brrrrrr, I guess.
Earlier quoted context omitted.
My life has been a lie. That sounds incredible.
To be fair - coffee cake in the US is cake to have with coffee and doesn’t normally contain any coffee. In the UK and EU, coffee cake is cake with coffee. Likewise tea cakes in the US are cakes made with tea and tea cakes in UK and EU are cakes to have with tea. So… Not a lie, just a Spider-Man meets Spider-Man moment when you learn you can actually make coffee cakes with coffee (or espresso) and you can make tea cak…
I can only imagine the kind of fascinating, or maybe frightening list of perceived requirements someone might need from their editor/ide that boils down to their installing this.
Major visual difference would be that whatever the editor font settings dictate, would apply to all the UX not just the text-editor tabs. But that, who would even mind.
The extensions compat would have to be NodeJS-based I guess, but the rest wouldn't have to be written in JS/TS I suppose..
Plenty of us are "happily Stockholmed" by the overall DX of VSCode but were there a Electron-less but otherwise 99+%-compat-and-keeping-up-with-vsc rendition (TUI or native GUI), we'd jump on it nonetheless.
I used micro for a while, which was quite pleasant, but didn't have all the LSP goodness.
Ctrl+Shift+←/→/ doesn't work, Shift+←/→/ at the end of line doesn't work, no quick access to console, so I will continue to use mcedit from mc instead.