Reading the link Justin posted, seems like this is a limitation resulting from the design of Vim.
Given this limitation, is there another way to run post-creation setup on *all* matching buffers, including those created for files specified on the CLI?
I need to set the filetype and run a bunch of setup commands on *.md buffers. BufNew was the only proper way I found to do this, and apparently I can't count on it to work in all cases.
Is there an alternative?
My current "workaround" has been to use BufRead instead. It is not optimal: it triggers every time the buffer is re-read, which is far more often than I need it to run (only once when the buffer is created).
--
--
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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment