Closed kovetskiy closed 9 years ago
Does it happen all the time? Which plugins do you use? (I tested it on Vim with a really little number of plugins)
I got the same issue if I open Vim (without filename) and e.g. open :help
after it.
Yep, it happens every time.
As I see it now, FileStyleActivate()
function is not called for some reason. Probably, I need to add another one evend listening.
Listening of the event VimEnter
fixed the issue in case of no file opened. Can you please let me know if it also resolves the issue for you?
diff --git a/plugin/filestyle.vim b/plugin/filestyle.vim
index 68572e4..273fee8 100644
--- a/plugin/filestyle.vim
+++ b/plugin/filestyle.vim
@@ -25,7 +25,7 @@ if !exists('g:filestyle_plugin')
"Defining auto commands
augroup filestyle_auto_commands
autocmd!
- autocmd BufReadPost,BufNewFile * call FileStyleActivate()
+ autocmd BufReadPost,BufNewFile,VimEnter * call FileStyleActivate()
autocmd FileType * call FileStyleCheckFiletype()
autocmd WinEnter * call FileStyleCheck()
augroup end
Nope, that does not resolve my problem.
You can try open any buffer like Unite/FuzzyFinder/Tagbar and get this message.
May I ask you run Vim with the following option:
vim -V20DebugLog
and upload the log saved as DebugLog
?
Thanks, I would like to know which events are not covered.
When I open any file, I get this message:
I fixed it through the
get()
function