Fix bug with highlighting in NerdTree windows

Editing a directory (and allowing NerdTree to intercept it) causes the
`BufWinEnter` autocmd to not fire, use `BufEnter` instead.

Clear `w:lsc_highlights_version` when clearing highlights, otherwise
re-entering a buffer with highlights will think it's fresh.

CHANGELOG.md

@@ -2,6 +2,9 @@
 
 - Add `:LSClientDocumentSymbol` command to populate the quickfix list with
   symbols in the current document.
+- Bug Fix: Clear highlighting when entering buffers that don't fire
+  `BufWinEnter` but do fire `BufEnter`. Restore highlights when opening a buffer
+  that in a window that previously had cleared highlights.
 
 # 0.2.9+1
 

autoload/lsc/highlights.vim

@@ -31,6 +31,9 @@ function! lsc#highlights#clear() abort
     endfor
   endif
   let w:lsc_diagnostic_matches = []
+  if exists('w:lsc_highlights_version')
+    unlet w:lsc_highlights_version
+  endif
 endfunction
 
 " If vim is in select or visual mode return true and attempt to schedule an

plugin/lsc.vim

@@ -56,11 +56,11 @@ augroup LSC
   " 1. Diagnostic highlights
   " 2. Diagnostic location list
   "
-  " The `BufWinEnter` event indicates most times when the buffer <-> window
+  " The `BufEnter` event indicates most times when the buffer <-> window
   " relationship can change. There are some exceptions where this event is not
   " fired such as `:split` and `:lopen` so `WinEnter` is used as a fallback with
   " a block to ensure it only happens once.
-  autocmd BufWinEnter * call LSCEnsureCurrentWindowState()
+  autocmd BufEnter * call LSCEnsureCurrentWindowState()
   autocmd WinEnter * call timer_start(1, function('<SID>OnWinEnter'))
 
   " Window local state is only correctly maintained for the current tab.