Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 783

A project that seeks to refactor Vim. Use this tag for questions specifically regarding Neovim-only features (i.e. features not found in Vim and other Vi-like editors).

1
vote
doing away with g:impact_transbg) yields the intended behavior in both vim and neovim even with set term=xterm and set t_Co=256 removed. This implies that with $TERM=xterm-256colors in both vim and … neovim, the conditional if exists("g:impact_transbg") fails, but that the combination of setting set term=xterm set t_co=256 allowed the conditional to succeed. Removing the if-else clause as …
answered Jun 15 '15 by Gall
16
votes
8answers
I don't have a full understanding of how my color scheme is interacting with the term setting in vim and this is impeding my ability to get it to display correctly in neovim. In my .vimrc file … ctermfg=Gray ctermbg=Black hi LineNr term=bold cterm=bold ctermfg=White ctermbg=Black endif In neovim, term cannot be set. I tried invoking neovim with a manually set $TERM like so …
asked Jun 13 '15 by Gall