Hari Krishna Dara wrote:
I am observing what might be inconsistency in the order in which vim
fires autocommands. First, ovserving the order of buffer and window events,
- Using :new:
WinLeave
WinEnter
BufLeave
BufEnter
- Using :wincmd w
BufLeave
WinLeave
WinEnter
BufEnter
I'm not sure I fully get what's going on, but I think is has to do
with the window that is automatically cloned to start the tab, which
is then converted to an empty buffer window.
On 5/15/06, Hari Krishna Dara [EMAIL PROTECTED] wrote:
Just wanted to send the script that I used, in case
I am observing what might be inconsistency in the order in which vim
fires autocommands. First, ovserving the order of buffer and window events,
- Using :new:
WinLeave
WinEnter
BufLeave
BufEnter
- Using :wincmd w
BufLeave
WinLeave
WinEnter
BufEnter
When combined with tab operations,
-
Just wanted to send the script that I used, in case anyone is interested
to repeat:
let g:auCount = 0
aug TT
au!
au WinEnter * :call Au('WinEnter')
au WinLeave * :call Au('WinLeave')
au TabEnter * :call Au('TabEnter')
au TabLeave * :call Au('TabLeave')
au BufEnter * :call
