Error Detected While Processing Bufread Autocommands For
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 192 Star 7,228 Fork 883 scrooloose/syntastic Code Issues 26 Pull requests 4 Projects 0 Wiki Pulse Graphs New issue Error detected while processing autocmd bufread BufRead Auto commands for "*" #1319 Closed myint opened this Issue Feb 10, 2015
Error Detected While Processing Vimenter Auto Commands For *
· 4 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants
Error Detected While Processing Bufwrite Auto Commands For Go
myint commented Feb 10, 2015 I get the error the following error message when I use :Errors: Error detected while processing BufRead Auto commands for "*": E492: Not an editor command: [Errno 2] No such
E20 Mark Not Set
file or directory: ''^@ This happens only if I have au BufRead * execute stuff in my Vim configuration. I intend this to match all filenames with the *. I know next to nothing about Vim syntax so I'm probably doing something wrong. If I replace it with au BufRead *.* execute stuff, :Errors no longer triggers the above error. But this causes files that do not have . no such highlight group name bad whitespace in them to not be matched. Should I be using something else instead of *? Thanks Collaborator lcd047 commented Feb 10, 2015 I can't reproduce this, and I don't really see how it could be related to syntastic. My guess would be it's either a problem in the way you wrote stuff, or a bug in Vim. What is your complete configuration? myint commented Feb 10, 2015 To reproduce it, use indent-finder: $ cd ~/.vim/bundle $ git clone https://github.com/myint/indent-finder $ cd indent-finder $ git checkout bec1640c8c827762c574f7df39fe720c51b9b6f9 Then open a file with errors in it with Vim. Run :SyntasticCheck. Then run :Errors. And here is my temporarily workaround. Thanks myint commented Feb 10, 2015 Here is a relevant screenshot. If I do press ENTER, the location list will then properly show up. myint commented Feb 10, 2015 Oh, I figured out what the problem was. I'm doing a system() call with the au BufRead * first and then get the results. The problem is this gets passed an empty string as argument to the system call. This results in an error message from the system call [Errno 2] No such file or directory: '' to be executed in the next line, which is au BufRead * execute. https://github.com/myint/indent-finder/blob/7f6a2c17a
Sign in Pricing Blog Support Search GitHub This repository Watch 25 Star 957 Fork 45 mhinz/vim-signify Code Issues 2 Pull requests 0 Projects 0 Pulse Graphs New issue error when writing file with no error detected while processing bufread auto commands for "*.py": e518: unknown option: set filetype #101 Closed justinmk opened this Issue Dec 4, 2013 · 7 comments Projects vim unknown option set None yet Labels not reproducable bug Milestone No milestone Assignees No one assigned 3 participants justinmk commented Dec no such highlight group name: badwhitespace 4, 2013 If I write/save a file that was restored from a session (which does not set up filetype autocmds, and &ft is empty), :writing the file causes: Error detected while processing BufWritePost Auto commands https://github.com/scrooloose/syntastic/issues/1319 for "*": E121: Undefined variable: b:sy_path E116: Invalid arguments for function sy#start Editing the file with :e to load the syntax/filetype plugins fixes the issue, even after setting :set ft= again (I guess because autocmds are already set up). I realize this is probably an edge case (I assume most people gave up on vim sessions), so I will try to debug it myself if it annoys me enough. Just https://github.com/mhinz/vim-signify/issues/101 putting it here to see if anyone else ran into it. I think it started happening since the last 5 or so commits. Owner mhinz commented Dec 4, 2013 Yes, it's quite reasonable that it started happened around 5 commits ago (when we switched from one fat global variable to buffer-local variables.) I can't really reproduce it, though. I just created a plain file with one sentence in it and saved it in a session (and of course people are still using sessions.. vim-startify! :D). I sourced that session under different circumstances: 1) non-VCS file 2) VCS file with no changes and 3) VCS file with changes, but it all seemed to work. If b:sy_path isn't set, it means that the BufRead/BufEnter events weren't triggered. Let me dig into it.. EDIT: I still can't reproduce it and I never used SessionLoadPost so far, but maybe this is enough already: change line 17 in plugin/signify.vim from: autocmd BufRead,BufEnter * let b:sy_path = resolve(expand('
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
processing BufLeave Auto commands" Kind bug Product Command-T When Created 2011-02-11T07:22:19Z, updated 2014-03-22T20:41:16Z Status closed Reporter Greg Hurrell Tags no tags Description From a user email: Hi Wincent, I've recently compiled and added your Command-T plugin to my recent compilation of Vim 7.3 on Mac OS X (using these options