111–120 of 120 posts
Earlier quoted context omitted.
It's very featureful and very easy to pick up. So I speculate that most of its popularity is with people that unfortunately have not yet been enlightened by vim/emacs.
I used Vim for several years before switching to Sublime Text 3.0 and now VS Code. VS Code support for TypeScript is just unmatched on any other editor.
Earlier quoted context omitted.
I use vim regularly on my day job. However, I am not familiar with more of the advanced side of things, and would never call myself an advanced user. That aside, I was always of the impression that vim was simply vi but extended in a sense. Is that not the case? How different is vi to vim?
In my eyes, vi is ok for system administration, but not for programming. The differences are not huge, but even if I have a "small" .vimrc with one single plugin, I have issues using the vim.tiny installed on Debian by default. The Vim help has a list of the differences: https://vimhelp.org/vim_faq.txt.html#faq-1.4 The most important to me are: - a real undo - buffers - macros (recorded on the fly with ththe q key) -…
I feel about Vim the way RMS seems to feel about Linux. Even though, (presumably) everyone knows the relationship of vim to vi, I don’t feel there is enough explicit acknowledgement of that fact. Vim is evidently a wonderful tool, (I say this as a confirmed 20 year emacs user for whom emacs is only usable due to excellent vi emulation possibilities) but it clearly wouldn’t exist without the basic foundation provided…
But...who cares? Yes, Vim owes a debt of gratitude to Bill Joy's vi. And vi was built from ex, which was built from ed, ad infinitum back to the dawn of computing. I like trivia, especially computer trivia, and I was there for much of this evolution. But it's not important to know any of it.
I think vi might more charitably be described as a paradigm shift. It also happened to bring terminal independence to everybody by later prompting the development of termcap (like vi, brought to us by Bill Joy). Of course termcap begat terminfo, [n]curses, ...
I feel like grandparent wishing for acknowledgement isn’t really out of line. It’s “Show a little respect; you have no idea where we were before vi.”
Earlier quoted context omitted.
This is reasonably fast, but not nearly as fast as if can be on Vim. IDK how GP did it, but one quick way might be searching for strings and hitting . whenever the macro needs to be applied. So you would end up doing something like n n n . n n . n n and so on, where each n means “go to next string” and each dot corresponds to finding and renaming something manually in other editors. You can go through dozens of occur…
The vscode rename is much simpler/faster than that - cursor over the symbol/variable, press F2, type in the new name, press enter. Renames all references across all files in your project. edit: no shade on VIM and VIM macros; they're great. I'm a very experienced vim power user, but have switched to vscode with vim keybindings, and I'm very very happy with the switch.
Earlier quoted context omitted.
I used Vim for a number of years (I'd guess around 10), and for the last year or so I've been using Spacemacs. I think there's so much that's great about both of them, and I'll continue to use one or the other, but geez, there's so many niggling issues with both that can be offputting. A couple of examples. In Spacemacs, the screen regularly goes blank for a while. Or if I have a file open in Spacemacs, close its win…
If you’re on macOS, the screen blanking is a known issue that’s happening because of some unknown interaction between the OS rendering and Emacs double buffering. IIRC, the mailing list thread about it concluded saying that nobody who wanted to work on the Emacs source had the requisite macOS knowledge to fix it and it’s been stuck there for a while?
Earlier quoted context omitted.
This is reasonably fast, but not nearly as fast as if can be on Vim. IDK how GP did it, but one quick way might be searching for strings and hitting . whenever the macro needs to be applied. So you would end up doing something like n n n . n n . n n and so on, where each n means “go to next string” and each dot corresponds to finding and renaming something manually in other editors. You can go through dozens of occur…
The vscode rename is much simpler/faster than that - cursor over the symbol/variable, press F2, type in the new name, press enter. Renames all references across all files in your project. edit: no shade on VIM and VIM macros; they're great. I'm a very experienced vim power user, but have switched to vscode with vim keybindings, and I'm very very happy with the switch.
Earlier quoted context omitted.
It's hard to sense how much of vi is in vim, having only ever used vim. But I've never been very happy with vim, even though I've used it for 15 years. Maybe I need to find a "vim, the good parts (aka vi)" book.
use spacemacs with vim emulation :-)
If you think Vim emulation is a replacement for Vim, either you don't know Vim or you don't like Vim. VSCode Vim emulation? Spacemacs? They are miniscule, pale comparisons. VSCode is a fine editor. Emacs is a fine editor. Spacemacs is pretty fantastic. But if you you think that's Vim, you simply don't know and appreciate Vim. That's ok, but it's not even in the same universe as the real thing. By all means use what y…
Earlier quoted context omitted.
This is unfortunately not uncommon. I feel like most of my coworkers at most companies Ive worked for don't use vim. One killer app of vim for me is macros. You can record a string of commands and map doing that to a letter. This makes certain mundane changes you have to do sometimes in software a breeze. For example, I had some code where someone was using string literals everywhere when they should have defined an…
> If I wasn't using vim I'd probably just leave that code as it was because it would have been so much effort. Most modern editors, Visual Studio Code included, have powerful refactoring abilities. Not only that, but they're usable without needing to be an editor expert - just right-clicking and selecting "Change all occurrences" (or pressing F2) does the trick.
Earlier quoted context omitted.
I spend a lot of time in tmux and I frequently open and close terminal sessions so I made this https://github.com/cboppert/motd It’s message of the day but with ViM tips. It worked fantastically for getting small tips throughout my day that allowed me to consume and learn without necessarily dedicating any tangible amount of time to it.
I love this idea! Basically a vim version of "fortune". Did you compile that list yourself?