4

Recently, the vim built into my Mac has started to show me linting feedback visually whenever I save. This is annoying and I'd rather it not happen. (Previous 20 years of using vi/vim did not have this behavior.)

My web searching suggests perhaps it's ALE, so I tried to disable it with :ALEToggle, but vim replied with "E492: Not an editor command: ALEToggle." So I don't think it's ALE.

The gutter shows many instances of S> as the indicator of where linting feedback resides, and then highlights characters within those lines as points of concern. See examples in screenshot below.

What linter uses S> and how do I disable it globally, for all files? I don't need or want this feature.

Screenshot of linting feedback in a Python file

The relevant parts of my ~/.exrc file are here. (Note that things like ^H had to be typed out, because trying to paste them here failed for obvious reasons.) There is a little more than this in my file, but everything not shown here I've tried commenting out and it doesn't help, so it's not the problem.

execute pathogen#infect()
set ai
set ts=4
syntax on
set expandtab
set nu
filetype indent off
set softtabstop=4
set shiftwidth=4
set smarttab
set hlsearch
set ignorecase
set t_Co=256
colorscheme wombat256mod
map ^H :nohlsearch<Enter>
set mouse=a
set relativenumber
Nathan
  • 1,451
  • 1
  • 15
  • 28
  • can you please include your `.vimrc`? – Josh Bode Aug 04 '20 at 09:33
  • 1
    @JoshBode Done, thank you. – Nathan Aug 04 '20 at 19:50
  • Thank you :) Also, can you please add the output of `set rtp?` to show what plugins are possibly being loaded on the runtime-path? And does the issue persist if you comment out the line `execute pathogen#infect()`? `:help local-additions` may also shine some light on any plugins being loaded. – Josh Bode Aug 05 '20 at 02:16
  • @JoshBode Progress! First, `set rtp` gave `runtimepath=~/.vim,~/.vim/bundle/julia-vim,~/.vim/bundle/nim.vim,~/.vim/bundle/sy ntastic,/usr/share/vim/vimfiles,/usr/share/vim/vim80,/usr/share/vim/vimfiles/after, ~/.vim/after`. Second, commenting out pathogen makes the problem go away. Third, running `:help local-additions` I don't think I understand the output fully, but I think it's saying my only local addition is `syntastic-checkers.txt`. – Nathan Aug 05 '20 at 13:31
  • By the way, I definitely recommend using something like [vim-plug](https://github.com/junegunn/vim-plug) as a more modern plugin manager over Pathogen - it's much more explicit about exactly what plugins are being loaded, and provides an update function to keep plugins fresh :) – Josh Bode Aug 08 '20 at 00:02

1 Answers1

5

It looks like you're getting style warnings from Syntastic.

Either you can remove the plugin by deleting ~/.vim/bundle/syntastic or you could try adding this to your Vim config:

let g:syntastic_mode_map = {"mode": "passive"}
Josh Bode
  • 3,582
  • 1
  • 27
  • 17
  • 1
    Very close! This helped put me on the path to the right answer, which is actually to use `g:syntastic_mode_map = {'mode':'passive'}` instead. But I want you to get credit, so please update the answer and I'll mark it as the accepted one. – Nathan Aug 06 '20 at 16:11
  • Great! Glad you got it fixed :) Otherwise, these things are just an endless distraction ;) – Josh Bode Aug 07 '20 at 10:47