Skip to content

close location list if initiating buffer is closed #123

Closed
y opened this Issue Dec 15, 2011 · 5 comments

3 participants

@y
y commented Dec 15, 2011

When editing a buffer and the location list is opened, and then the original buffer is closed, the location list remains open. I think the location list should also close if the initiating buffer is closed.

@scrooloose
Owner

An interesting point, but this is not an issue with syntastic - its an issue with vim itself. Ill leave this issue open for now while I think about it (and see if anyone else has any comments).

Changing vims behaviour like that doesnt feel like a good idea though.

@y
y commented Dec 15, 2011

Fair enough, I just noticed that's how the quickfix window functions as well. I guess a simple solution would be to mention in the docs how to accomplish this with an autocmd.

@millermedeiros millermedeiros added a commit to millermedeiros/syntastic that referenced this issue Dec 16, 2011
@millermedeiros millermedeiros auto close location list when closing or moving to another buffer. al…
…so update errors on BufEnter. see #123
0d1943e
@millermedeiros

attached the pull request and commit in case you guys decide to add it (or anyone else wants to do it as well..) - I will keep it on my local copy for sure, this always annoyed me :D

@millermedeiros millermedeiros added a commit to millermedeiros/syntastic that referenced this issue Dec 16, 2011
@millermedeiros millermedeiros fix loc list auto close. see #123
 - changed BufLeave to BufWinLeave otherwise it would close when
   jumping to loc list.
 - extracted method that auto close/open location list based on
   errors/settings and make sure it reopens loclist when buffer is
   displayed (BufWinEnter) if needed.
d3b122d
@millermedeiros

FYI, this was merged into master December 16, 2011

@scrooloose
Owner

Sweet, closing :)

@scrooloose scrooloose closed this Jan 6, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.