I am working on a project for a long time. I pushed it to GitHub yesterday.
Today when I am trying to edit files with neovim or vim, it shows an exclamation mark on the left side of the line number if I edit any lines. I have edited lines 13 and 17. You can see the exclamation marks on the picture below.
It's really irritating me. Is there any way to remove these exclamation marks? It did not happen before I pushed it to Git. I think this has something to do with Git.
This is the result of the vim-signify plugin (https://github.com/mhinz/vim-signify). Just remove line 124 and run :PlugClean.
EDIT: line 124 refers to the OP's ~/.vimrc file. It reads Plug 'mhinz/vim-signify' and indicates to the vim-plug plugin manager to install vim-signify.
Related
I was installing some packages via pathogen and did not like one of the color themes and deleted those packages via terminal.
Ever since then when I execute vim thankYou.js ( :) ), I get this.
Failed. HELP
How do I remove those '--- options --' and confirmations? I just want to go straight to vim.
Thanks in advance ;)
You should try following the explanation at on Vim-FAQ 2.5:
2.5. I have a "xyz" (some) problem with Vim. How do I determine it is a
problem with my setup or with Vim? / Have I found a bug in Vim?
(...)
vim -u ~/.vimrc --noplugin -N -i NONE
This will simply use your .vimrc as configuration file, but not load
any plugins. If the error occurs this time, the error is possibly
caused by some configuration option inside your .vimrc file. Depending
on the length of your vimrc file, it can be quite hard to trace the
origin within that file.
The best way is to add :finish command in the middle of your .vimrc.
Then restart again using the same command line. If the error still
occurs, the bug must be caused because of a setting in the first half
of your .vimrc. If it doesn't happen, the problematic setting must be
in the second half of your .vimrc. So move the :finish command to the
middle of that half, of which you know that triggers the error and
move your way along, until you find the problematic option. If your
.vimrc is 350 lines long, you need at a maximum 9 tries to find the
offending line (in practise, this can often be further reduced, since
often lines depend on each other).
If the problem does not occur, when only loading your .vimrc file, the
error must be caused by a plugin or another runtime file (indent
autoload or syntax script). Check the output of the :scriptnames
command to see what files have been loaded and for each one try to
disable each one by one and see which one triggers the bug. Often
files that are loaded by vim, have a simple configuration variable to
disable them, but you need to check inside each file separately.
I've had this issue often where if I compile vim myself on a server (due to lack of root permissions), at various times, I'll get garbled lines in vim when I have split windows. This is hard to describe, and thus hard to search for, as well.
Here's an image of a vim window. In each split is my .vimrc. Everything is good right now:
Now, I hit some in the right split to scroll down, and suddenly, we have garbled text and line 176 showing up everywhere:
This is not particular to any specific file. I've tried removing all my plugins, and the issue persists.
It turns out, the offending line was
set encoding=utf-8
in my .vimrc. I basically commented out my entire vimrc, and searched through until I realized this line was the issue, and I'm not entirely sure why.
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
I'm very accustomed to typing `. when I open a file to resume editing where I last left off.
On the default Vim 7.3 that came with my new OS X 10.9 Macbook this behavior doesn't work... it says E20: Mark not set. Any idea how to enable this? When I type:
:set viminfo?
I see that viminfo appears to be set to something reasonable:
viminfo='100,<50,s10,h
[UPDATE: Turns out my .viminfo file was owned by root for some reason. Using chmod to change owner back to myself solved the problem.]
I reproduced your problem on my Ubuntu machine. The original output of set viminfo? was just like yours.
viminfo='100,<50,s10,h
After putting the following line in my .vimrc, I was able to jump to the former cursor location using
`.
set viminfo='10,\"100,:20,%,n~/.viminfo
I got that line from this vim tip, where each part is also described.
Update: The OP already solved his problem, which was related to permissions on .viminfo, but I am leaving this answer up in case it helps future people who did not have that particular issue.
I recently upgraded to Komodo Edit 7 from v6. In previous versions if I was adding tabs to the beginning of lines I could press down and the cursor would automatically move to the beginning of the next line. The net effect meant that to indent a whole bunch of line I just had to press DOWN and TAB repeatedly
Since I've upgraded it no longer works like this. If I press TAB at the beginning of a line and then down, it indents the first line, then moves to the next line, one tab width in.
Does anyone know how to re-enable this functionality on Komodo Edit 7, or whether it was completely removed?
I am experiencing the same issue. As Paul Sweatte suggests, there is an alternate way to indent a group of lines (adding tabs at the beginning), but no alternative exists for doing this in the middle of a group of lines.
I have submitted a bug here: http://bugs.activestate.com/show_bug.cgi?id=94104
Update: Bug status has been updated to Resolved. This should be fixed in the next release (7.1.0) or you can download the nightly build: http://downloads.activestate.com/Komodo/nightly/