Skip to content
This repository has been archived by the owner on Apr 29, 2021. It is now read-only.

Commit

Permalink
Remove Syntastic 'cause it gets too much in the way.
Browse files Browse the repository at this point in the history 
It has a bad habit of automatically closing my location lists
(see vim-syntastic/syntastic#637).
  • Loading branch information
Lifepillar committed Aug 20, 2015
1 parent 905753e commit 66f2a86
Show file tree
Hide file tree
Showing 3 changed files with 1 addition and 19 deletions.
3 changes: 0 additions & 3 deletions .gitmodules
View file
Expand Up @@ -73,9 +73,6 @@
[submodule "bundle/rust"]
path = bundle/rust
url = https://github.com/rust-lang/rust.vim.git
[submodule "bundle/syntastic"]
path = bundle/syntastic
url = https://github.com/scrooloose/syntastic.git
[submodule "bundle/ultisnips"]
path = bundle/ultisnips
url = https://github.com/SirVer/ultisnips.git
Expand Down
1 change: 0 additions & 1 deletion bundle/syntastic
Submodule syntastic deleted from 47c70b
16 changes: 1 addition & 15 deletions vimrc
View file
Expand Up @@ -702,7 +702,7 @@
\ %#SepMode#%{w:["lf_active"] && w:["lf_winwd"] >= 60 ? g:right_sep_sym : ""}
\%#CurrMode#%{w:["lf_active"] ? (w:["lf_winwd"] < 60 ? ""
\ : g:pad . printf(" %d:%-2d %2d%% ", line("."), virtcol("."), 100 * line(".") / line("$"))) : ""}
\%#Warnings#%{w:["lf_active"] ? SyntasticStatuslineFlag() . (exists("b:stl_warnings") ? b:stl_warnings : "") : ""}%*'
\%#Warnings#%{w:["lf_active"] && exists("b:stl_warnings") ? b:stl_warnings : ""}%*'
endf

fun! s:enableStatusLine()
Expand Down Expand Up @@ -874,20 +874,6 @@
nnoremap <silent> <leader>m :call <sid>toggleShowMarks()<cr>
nnoremap ` :ShowMarksOnce<cr>`
" }}
" Syntastic {{
let g:syntastic_check_on_open = 0
let g:syntastic_check_on_wq = 0
let g:syntastic_cursor_columns = 0
let g:syntastic_error_symbol = '⦿'
let g:syntastic_warning_symbol = '●'
let g:syntastic_style_error_symbol = '»'
let g:syntastic_style_warning_symbol = '»'
let g:syntastic_always_populate_loc_list = 1
let g:syntastic_auto_loc_list = 1
let g:syntastic_loc_list_height = 5
let g:syntastic_aggregate_errors = 1
let g:syntastic_stl_format = ' %E{Err: %fe}%B{ }%W{Warn: %fw} '
" }}
" Tagbar {{
fun! TagbarStatusLine(current, sort, fname, flags, ...) abort
return a:current ?
Expand Down

4 comments on commit 66f2a86

@lcd047
Copy link

@lcd047 lcd047 commented on 66f2a86 May 2, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or you could just read the manual, then set g:syntastic_auto_loc_list to 3.

@lifepillar
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I'll give it a try and let you know if it works. I am pretty sure I had read the manual, but right now I don't remember why I had set g:syntastic_auto_loc_list to 1 instead of 3.

@lifepillar
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, g:syntastic_auto_loc_list set to 1 is what I want, because I do want Syntastic's location list close automatically. The problem I have with that setting is that, if I have another buffer with a different location list opened (unrelated to Syntastic), that one gets closed, too, when I switch to that buffer. That's what I find annoying.

Setting g:syntastic_auto_loc_list to 3 fixes the problem, although it means that I have to close Syntastic's location list manually.

At the time of this commit, I had determined that the problem was somehow related to the issue I have linked to, although right now I don't recall the details.

@lcd047
Copy link

@lcd047 lcd047 commented on 66f2a86 May 3, 2016 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's related, sort of, but the root of the problem is in Vim's API, not in syntatsic: given a location list, there is no way to tell which buffer "owns" it, nor which window it belongs to. Consequently the problem won't be fixed until it's fixed in Vim's API, and that, realistically, won't happen in the foreseeable future. shrug

Please sign in to comment.