Vim Anti-Patterns That Cause Beginners To:Quit • Hacker News Board

Re: Vim Anti-Patterns That Cause Beginners To:Quit

#131

Post by rendall » Sat, Oct 09, 2021, 6:06 AM UTC

stnmtn wrote: post #109

afiori wrote: post #22

Earlier quoted context omitted.

trackpads are the keyboard, on ThinkPad laptop for example you can use it entirely with only your thumbs.

How do you handle having to change a function's parameters, for instance? In vim, you just have your cursor inside the (...) and do `ci)`, which is (c)hange (i)nside `(, which instantly deletes all the test inside the (...) and you can type that stuff out easily For a trackpad, don't you have to manually select all that text, hit delete, then start typing again? Or is there a better way I'm not thinking of

So. Many. Shortcuts. And, if you use it as an extension to your IDE, say for VSCode, you can still use your pointer.

Delete to line's end: d$ Delete to next blank line: d] Replace current character: r Surround the next 3 words with quotes: ys3w" (non standard, but out-of-the-box on VSCode)

On and on

Re: Vim Anti-Patterns That Cause Beginners To:Quit

#132

Post by markenqualitaet » Sat, Oct 09, 2021, 11:28 AM UTC

justinsaccount wrote: post #97

markenqualitaet wrote: post #93

Personally I think, whatever ctrl-s is doing instead of saving, is the only really hostile default in vim. To a beginner it's the "mysteriously break vim for good" shortcut. And maybe the lack of ctrl-c/-v clipboard management. I hate pasting things into default vim.

That is not vim, ctrl-s/control-q turn on/off flow control. Very useful if you want to temporarily pause command output. You can turn it off using `stty -ixon`, and this also wouldn't be a problem in a graphical vim, but vim would need to have a keybinding for it.

Oh, yeah right. Thanks. I forgot the details there. This even goes to your e.g. .bashrc right?

Tho, couldn't vim overwrite this somehow?

In any case, this legacy feature is a major pain in the ass for beginners. Today ctrl-s/-c/-v and maybe ctrl-z have another meaning IMO and sticking to legacy is messing with heads unnecessarily. Pantheon terminal manages to e.g. make ctrl-c context dependent copy/cancel.

Re: Vim Anti-Patterns That Cause Beginners To:Quit

#133

Post by siproprio » Sun, Oct 10, 2021, 1:55 AM UTC

xwolfi wrote: post #112

drekipus wrote: post #17

There's been a number of "anti-vim, use a real ide(TM)" posts coming into my feed lately and I don't get why. Do people really get buttmad about this? I switched from vscode to vim as I found it to be largely much faster in getting around when I started my new job, some people find the opposite. A ok. Why do people try to force us into these largely closed solutions? ( Mainly it's vscode, which has a real EEE threat)

It's the time wasted. Look at a guy merging 30 conflicts in text mode for an hour :D I think there can be clever specialized vim gurus, but god the ones I work with just struggle so much while idiot me click 3 buttons in an IDE and move on. We're not paid to be clever, we're paid to make money.

> god the ones I work with just struggle so much while idiot me click 3 buttons in an IDE and move on.

Like I said in the other thread about vscode:

If you assume whatever's been done here's been done wrong it saves the company time and money, we know it's fucked up that's why we called you.

Re: Vim Anti-Patterns That Cause Beginners To:Quit

#134

Post by markenqualitaet » Sun, Oct 10, 2021, 11:05 AM UTC

throwawake wrote: post #104

markenqualitaet wrote: post #79

Earlier quoted context omitted.

Does (neo)vim offer a similar debugging experience? Visually stepping through code and setting break points and stuff? I like vim's code navigation, but I miss the autocompletion features of bigger editors. Can you make vim tab complete like sublime? Last I tried, it was never as "one key to rule them all", but required some additional finger-fu and attention. Also moving selected code around (so I can make engine no…

Debugging is one of the reasons I keep using vscode. There is vimspector but I never tried that. For code-completions coc.nvim offers similar config and plugins as vscode. There is official lsp support for neovim now but coc.nvim works fine.

Thanks.

Re: Vim Anti-Patterns That Cause Beginners To:Quit

#135

Post by stnmtn » Tue, Oct 12, 2021, 4:25 AM UTC

rendall wrote: post #131

stnmtn wrote: post #109

Earlier quoted context omitted.

How do you handle having to change a function's parameters, for instance? In vim, you just have your cursor inside the (...) and do `ci)`, which is (c)hange (i)nside `(, which instantly deletes all the test inside the (...) and you can type that stuff out easily For a trackpad, don't you have to manually select all that text, hit delete, then start typing again? Or is there a better way I'm not thinking of

So. Many. Shortcuts. And, if you use it as an extension to your IDE, say for VSCode, you can still use your pointer . Delete to line's end: d$ Delete to next blank line: d] Replace current character: r Surround the next 3 words with quotes: ys3w" (non standard, but out-of-the-box on VSCode) On and on

Yep, using Vim in VSCode is just about everything I could ever want