11–20 of 27 posts
they're global marks in vim. no one uses them there because those registers are reused for clipboard history
the vscode extension doesn't implement registers this way so they're safe to use. i imagine zed's implementation is similar
used to think this mattered a lot but funnily one of the main vim-universe inspired editors, helix, has convinced me otherwise their choice to subtly diverge from the vim way of things is actually super nice, somehow way more mnemonic and easy to remember and use everyday
I find the helix model of select then act so much more aligned to my mental model. Rather than verb then noun in vim.
Vim register handling on deletion is pure crap. (delete a line lands into a different register than delete a word, pasting over a selection overrides the default register etc.).
There is one plugin in vim that I cannot live without though, and that is easymotion (there are other similar plugins). It highlights objects with a letter (like the start of words for example), pressing the letter jumps to the object. I find this so much more natural and easier than jumping to line numbers. I might have to implement this into helix ;)
"Vim mode" in editors like Zed is great and all, but to me, Vim is much more than just a set of shortcuts. What I love about Vim is how seamlessly it integrates with the terminal and shell. I can pipe, redirect, and manipulate text with Bash, use any CLI tool, and move fluidly between my editor and my system. The terminal is insanely fast, works on any computer and OS, scriptable, and gives me access to everything I…
I believe that the use case you describe is a bit different than where you would use Zed primarily. If I have a code base with 100k lines of code, and I am developing that, I don't hop from terminal to editor and back by using the same terminal instance. I have different terminal window for that. Closing the editor window would lose too much context.
"Vim mode" in editors like Zed is great and all, but to me, Vim is much more than just a set of shortcuts. What I love about Vim is how seamlessly it integrates with the terminal and shell. I can pipe, redirect, and manipulate text with Bash, use any CLI tool, and move fluidly between my editor and my system. The terminal is insanely fast, works on any computer and OS, scriptable, and gives me access to everything I…
I believe that the use case you describe is a bit different than where you would use Zed primarily. If I have a code base with 100k lines of code, and I am developing that, I don't hop from terminal to editor and back by using the same terminal instance. I have different terminal window for that. Closing the editor window would lose too much context.
When Zed got released, I was looking forward to trying it out because I saw the potential. Very soon I found out that: Vim mode must be perfect and few of my key combos have made me (Neo)vim addict. And also, I prefer terminal editor.
How does this company make money?
How does this company make money?
I’m not sure that they do, and that’s why I switched back to Vim from Zed. I can’t let myself build a skillset on a company’s product that’s liable to disappear in a few years.
"Vim mode" in editors like Zed is great and all, but to me, Vim is much more than just a set of shortcuts. What I love about Vim is how seamlessly it integrates with the terminal and shell. I can pipe, redirect, and manipulate text with Bash, use any CLI tool, and move fluidly between my editor and my system. The terminal is insanely fast, works on any computer and OS, scriptable, and gives me access to everything I…
Terminal is not insanely fast. UI wise it is not efficient. Rendering is slower than vscode too even with GPU powered terms
And most fast terminals these days use GPU rendering.