Hi ZyX!
On Fr, 28 Sep 2012, ZyX wrote:
> > It is not triggered when current and unloaded buffers are different, but
> > when it triggers, current buffer and buffer being unloaded might be
> > different. That is bufnr('%') can be different then "<afile>".
>
> Is not that what I said?
No.
>
> > You should not move to another buffer and probably you shouldn't change
> > a buffer as well as this might cause problems. I don't see, how
> > resetting the actions being done by a filetype script might cause
> > problems in this case.
>
> Actions done by filetype plugins are likely setting local options
> using setlocal. If you don’t move to another buffer you are setting
> local options *for a wrong buffer*. If you do you have other problems.
> Hence you must not use this autocommand.
No you are not. Just test it. It works correctly.
> > I disagree. The autocommand is there for a reason. Unsetting the
> > effects by a filetype plugin can be a reason to use this event.
Still holds.
regards,
Christian
--
--
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
