[flagged]
According to the Lindy Effect, we can expect such articles to continue until 2060. I personally feel that vim and it's derivatives will be with us as long as our civilization supports computing.
111–120 of 179 posts
[flagged]
According to the Lindy Effect, we can expect such articles to continue until 2060. I personally feel that vim and it's derivatives will be with us as long as our civilization supports computing.
How do you explain "w" and "wq" to save and quit the editor with "verb adjective object" model? These two and "i" is all I remember about vi. Or is vi a different thing from vim and this model doesn't apply?
I don't understand why people keep talking about :wq when :x has been a thing for so long now
Earlier quoted context omitted.
Well said. I use nvim with all kinds of plugins and a custom init.lua, and then I use vim (or nvi) when something goes wrong with my init.lua, and nvim won't start, or when I want to quickly open a file really quickly and not wait the second or so it takes for my nvim setup to load. Likewise, vim lets me do local editing on any system I connect to as there's rarely ever a Unix left that doesn't have vim installed. (B…
Would you mind sharing the python setup? So many options and it’s overwhelming for someone looking to switch from vscode.
- `blink.lua` (auto complete drop-down) - `dap.lua` (debugger) - `lsp.lua` (language server ruff and pyright setup)
It may also be because the terminal view is much smaller than vscode's smaller navigation font so I can see much less of the file tree in a terminal program such as ranger.
I also never really mastered windows although I did master vim buffers.
I do use tmux.
Agree that Vim is a language to talk to your computer, but it's not necessarily efficient. Vim is famously an imperative editor: You have to tell Vim the sequence of steps to perform. Clicking your mouse on a position on the screen is declarative: You declare you want the cursor here. With Vim you have to imperatively walk the cursor to where you want to go, or god forbid use something like easymotion.
set incsearch Now use / (+ n or N) + Enter to move around Done
This even works as a motion (e.g. d / foo, then ctrl G until you hit the right foo, then enter to delete until there).
Earlier quoted context omitted.
The reason I chose Vim over Emacs is simply because of the fact that it's available literally EVERYWHERE. I've honestly never seen a UNIX system which doesn't have Vi or Vim installed by default. Emacs is more hit and miss.
What does Vim offer over Nano? After using both I settled on Nano years ago and still don't see how my workflow would improve with Vim.
Vim is not only an editing language, but a fast-starting editor with a small-ish native executable, and small run-time memory use. This facet is typically not ported into other editors that have a Vim mode. Vim runs natively inside virtual machines and containers, on resource-constrained embedded systems, and on remotely accessed machines. Another aspect is that Vim can be operated entirely using a terminal emulator,…
So does nano
It's not as widely preinstalled, and has a poor editing language. If you can breathe with your mouth closed, you want something else.
Vim is not only an editing language, but a fast-starting editor with a small-ish native executable, and small run-time memory use. This facet is typically not ported into other editors that have a Vim mode. Vim runs natively inside virtual machines and containers, on resource-constrained embedded systems, and on remotely accessed machines. Another aspect is that Vim can be operated entirely using a terminal emulator,…
Well said. I use nvim with all kinds of plugins and a custom init.lua, and then I use vim (or nvi) when something goes wrong with my init.lua, and nvim won't start, or when I want to quickly open a file really quickly and not wait the second or so it takes for my nvim setup to load. Likewise, vim lets me do local editing on any system I connect to as there's rarely ever a Unix left that doesn't have vim installed. (B…
Earlier quoted context omitted.
And meanwhile in every thread or article about vim, it is very rare to mention remapping Caps Lock to Escape (or the other lesser IMHO lesser options ) even though one third of user do it. The other two third are deluded tool fetishists that are ready to suffer that their most important key is the furthest away from the home of row because "you get used to it" even if that's just an unfortunate historical accident. I…
> it is very rare to mention remapping Caps Lock to Escape I change mine to Ctrl. This way escape for me is Ctrl + [. Ctrl is too useful to be in an awkward position.
Earlier quoted context omitted.
Would you mind sharing the python setup? So many options and it’s overwhelming for someone looking to switch from vscode.
nvim/.config/nvim/lua/plugins - `blink.lua` (auto complete drop-down) - `dap.lua` (debugger) - `lsp.lua` (language server ruff and pyright setup)