Vim line numbers get garbled in tmux - vim

Running tmux on WSL Ubuntu 20, vim line numbers occasionally get fouled up. For example, in the below screenshot, line numbering is somehow disabled at line 4, and the corresponding text is left-shifted:

One workaround is to issue a redraw command (e.g., CTRL-L).

Related

How to remove extra blank line under command-line in vim/macvim?

I am getting this empty blank line below command-line. I had vim-airline installed but even after uninstalling it, the blank line is still there. (In full-screen mode)
With Airline installed
With Airline uninstalled
I have also tried to check cmdheight with :set cmdheight? and it is set to one in either case. Like wise :set laststatus? is also one.
When I exit out of full-screen the window will not resize below command-line.
How do I get rid of this blank line and possibly keep vim-airline?

Fix automatic lines in GVIM

I'm writing script in TCL and want to know, how can I fix the beginning of each line automatic?
each line begin is different tab amount and I want to fix it automatically?
In Emacs I know I can press TAB each line to reorder start line position.
How can I do it in GVIM?

How does one go to a specific line with vs code with vim?

I thought it was surprising that : doesn't even seem to open the vim last line mode but when I do:
:10
nothing happens. Which I thought was weird. Anyone know how to make vs code go to a line using vim commands?
I am using: https://marketplace.visualstudio.com/items?itemName=vscodevim.vim
Resources:
related git issue: https://github.com/VSCodeVim/Vim/issues/1889
reddit: https://www.reddit.com/r/vscode/comments/etfy37/how_does_one_go_to_a_specific_line_with_vs_code/
To get into command mode with vim in vscode or just regular vim, you simply type the esc key.
https://alvinalexander.com/linux/vim-vi-mode-editor-command-insert-mode
The exact commands that worked for me are in this order
First go to command mode by hitting the ESC key
Then type the line number 10
Then G
Or while in command mode go to last line mode with :. The colon while appear at the bottom in the blue section of vs code:

Why does vim sometimes display linebreaks incorrectly?

I have a long line of text in vim, soft-wrap is on, I've done :set linebreak, and breakat has the right value.
The problem is, when I edit some text in the middle of the "paragraph", the lines don't wrap at word boundaries anymore.
Example:
1) Cursor is in the middle of the line:
2) I type cw and the linebreaks change:
It stays like that when I go back to normal mode, but wraps correctly again when the cursor leaves the line.
This does not happen if I add text in the middle, or do a command like dw - seemingly just commands that delete some text and enter insert mode.
The problem began on a fresh install of Fedora 21, but my .vimrc is unchanged from my previous computer, where I did not have this problem.
How do I restore the correct behavior, or is this perhaps a bug in the Fedora package?
I believe, this is a bug, that has been fixed with 7.4.576

.vimrc causes error (E10: \ should be followed by /, ? or &)

I've copy pasted this .vimrc into my /etc/vimrc in Fedora 15. Every time I use vim for anything, I get a number of errors with line numbers which don't seem to be the correct line numbers of my vimrc file because there aren't any '\'s on those lines.
I've googled this and there is a similar stack overflow question, but I believe it is irrelevant to my question.
I also removed everything that said MySys() == linux/max/windows or etc because I'm using linux so I just used the linux lines.
Any ideas?
Edit---
Here's my (barely) modified vimrc file:
https://docs.google.com/document/d/1PznK0FizGlBr6W6m9wikM334q8b6KFFCgmsF-f8MX3s/edit?hl=en_US
Error you mentioned here normally happens in one of the following cases:
You are trying to use line continuation inside :execute.
You are trying to use line continuation when vim is in compatible mode.
To remove the second case run vim using vim -N. If no errors appear, add set nocompatible at the top of the vimrc. If errors still appear, search for exe (as :execute can be truncated to :exe) and check out whether somewhere line matching \n\s*\\ is passed to :execute.

Resources