It appears that &buftype is not correctly set with the BufEnter autocommand for a cmdline-window.
I've noticed this with a BufEnter autocommand that checks for &buftype, and the documentation states that it should be "nofile" for the cmdline-window, but it's empty. Additionally, according to the documentation, BufEnter shouldn't get triggered at all for a cmdline-window (from cmdline.txt): > Two autocommand events are used: |CmdwinEnter| and |CmdwinLeave|. Since this window is of a special type, the WinEnter, WinLeave, BufEnter and BufLeave events are not triggered. I've seen a similar oddity before, where &buftype appeared to be not current with a WinEnter autocommand, and in that case it helped to use BufEnter. Regards, Daniel. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
