On May 25, Christian Brabandt wrote: > [...] > > I am not sure, if this behaviour is a bug. However after > thinking some more about it, I am wondering, whether the > fact that the BufNew autocommand triggers a FileType > autocommand is a bug itself, since autocommands shouldn't > nest (see :h autocmd-nested). But I haven't looked into > the detail, why the FileType autocommand is triggered. > (And I have a feeling, that when this behaviour is > changed, it might actually break a lot of ftdetect > scripts.)
I was under the impression that nesting only applied to :e and :w. The documentation at `:h setfiletype` implies to me that it does nest, hence the inclusion of that command. You can even set 'ft' within a FileType autocommand and then trigger a different FileType autocommand. --Antony -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
