[38]

honestly Vim is pretty slow, and it utterly sucks with long lines. you can do "g" motion, but I cant seem to get my muscle memory to remember that. to me "down" should always use whats visible on the screen, not just dumbly move to the next line.

[umanwizard]

From a colleague; I haven’t tested it:

    --Remap for dealing with word wrap
    vim.keymap.set({ 'n', 'v' }, 'k', "v:count == 0 ? 'gk' : 'k'", { noremap = true, expr = true, silent = true })
    vim.keymap.set({ 'n', 'v' }, 'j', "v:count == 0 ? 'gj' : 'j'", { noremap = true, expr = true, silent = true })

[38]

what is this? I dont recognize that language

[auscompgeek]

It's Lua. Presumably they're using Neovim.

[umanwizard]

Ah, my bad. Not a heavy vim user so I didn’t realize this was neovim-specific.

[jasonjmcghee]

vimscript

[38]

No, it's not.

[jasonjmcghee]

mea culpa

[ntrz]

> you can do "g" motion, but I cant seem to get my muscle memory to remember that. to me "down" should always use whats visible on the screen, not just dumbly move to the next line.

You could always add key mappings to your .vimrc file so it works this way.

[xk_id]

you're supposed to learn the mechanics of vim and then configure it in a way which you find intuitive. i find that much more natural than software which tries to anticipate (and indirectly reinforce) some arbitrary "common sense".

  nnoremap <silent> k gk
  nnoremap <silent> j gj
  nnoremap <silent> 0 g0
  nnoremap <silent> $ g$

[chromoblob]

I have mapped gk and gj for Up and Down keys. So I can use both.

[Exuma]

Ok I got you mane.. you have 2 solutions. By the way, there is a sort of "common" set of configurations that probably 90% of people have in their vim config, like turning off the bell and stuff. Obviously there are exceptions because those people know what they're doing, but my point is that don't give up on it until you at least try a common config to remove a lot of the basic annoyances.

Solution 1: Add this to your vimrc. This will make it so when going up and down, wrapped lines are properly interpreted and not skipped

``` " better up and down map j gj map k gk ```

Solution 2: If you want to make it where the cursor literally goes ANYWHERE in the document, including in space that doesn't even exist, do this below. I used this mode for a very long time and it's amazing. I only switched recently just to try something new to see if I like it more, and right now I'm just 50/50 on if its better or not

``` " allow cursor to go anywhere set virtualedit=all ```

Lastly, try using `vimtutor` from terminal and practice commands right there in your terminal.

And, if by "slow" you are talking about literal performance, try Neovim. Neovim is basically a fork of nvim that gets rid of vimscript (but still allows it if you want to use it) and instead implements Lua, which is an extremely (the fastest, actually) scripting language. (The other comment you asked about was a Neovim lua configuration which does the same thing as the vimscript version).

Part of the Neovim idea is that they also set a lot more "sane" default config thats more modern.

The best part about Neovim is that it supports LSP's in a much better way, so you can complete VS-Code like IDE experience, rather than relying on a complex array of plugins. If you decide to do that, check out lsp-zero for the easiest setup possible.

If you decide to give neovim a shot, I would 100% recommend using this: https://github.com/nvim-lua/kickstart.nvim

I recently transferred 10+ year vim config to lua and neovim, and I saw people recommending this over and over. Because I wasnt familiar with it I thought "I dont need that, i want to start fresh". Well after doing that for nearly a month, I realized how good kickstart is, it REALLY is quite good, and does lots and lots that you would want without doing too much. I didnt use it, but i took tons of inspiration from it for setting up LSPs.

Let me know if you have any questions I'd love to not lose vim friend over something stupid like moving on long lines.