Re-opening the buffer doesn't necessarily issue a FileType event. I
found that if I *changed* the filetype explicitly, then the syntax
returned to normal. I'm guessing that the "state leftover" is that it
has simply missed the reason to update its syntax, and won't update
until it is given anothe
On Mon, 17 Apr 2006 at 5:08pm, Eric Arnold wrote:
> This is because you are ignoring the "filetype" event.
>
> Try a "doautoall FileType" when you're done.
>
Thanks, this means I can use :bufdo doautocmd FileType syntax, because I
also use :windo and :argdo in place of :bufdo.
I still wonder wh
This is because you are ignoring the "filetype" event.
Try a "doautoall FileType" when you're done.
On 4/17/06, Hari Krishna Dara <[EMAIL PROTECTED]> wrote:
>
> In my script, I am running a :bufdo command with eventignore=all because
> of two main reasons:
> - performs better as I am not trigge
In my script, I am running a :bufdo command with eventignore=all because
of two main reasons:
- performs better as I am not triggering any events.
- doesn't interfere with plugins that deal with MRU buffer lists.
This however leaves a side effect after the command is run. All the
buffer go into s
