New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a new source code buffer open when run finished #58
Comments
It's not supposed to happen, and I cannot reproduce your issue. Can you provide more information, e.g. the source file you have problem with, and your OS and vim version. Thanks! |
The code to reproduce this issue is rather simple: #include <stdio.h>
int main(int argc, char *argv[])
{
/* leave a warning intentionally: */
printf("%d\n",sizeof(int));
return 0;
} Here, a warning will be found by clang. My OS is Here is a screen-shot after executing: |
@lookforit Sorry that I cannot really find a solution at this moment. The problem is that |
hope this issue will be fixed in the further release. |
I'm using boost headers and they're full of warnings using clang with |
@xuhdev Isn't his issue regarding jumping to the warning, not the warning in the quickfix window? I have the same problem as him I believe. Coudn't SingleCompile provide altenative |
No you have different problems. @oblitum |
@xuhdev Yes thanks!, it has stopped doing that. |
@xuhdev also, contrary to what you said, it's still opening the quickfix automatically after compiling, so now it's working 100% :-) |
I've noticed trying this on Arch doesn't work. The plugin stopped working, although it works on Mac. On Arch also, the fix is unnecessary for me. It just works as expected. |
I think this is an issue in Vim internally. Do you use your MacVim from homebrew? What if you revert to the same Vim version on Arch? Are you using gvim on both OSes? |
I'm using MacVim yes, I had just updated it, still same behavior, it's from homebrew --HEAD:
On Arch it was a very recent one too I guess, since I had just setup the machine this week. It was installed with pacman. Even though it's MacVim, I'm not using graphical frontends, just terminal versions. |
by the way, in any case, it does still jumps to the quickfix buffer when it's set to open automatically, which I guess is the original reason of this issue. But it's less annoying than opening the buffer with the error too. |
I've uninstalled MacVim and installed raw Vim with homebrew --HEAD, still same behavior. |
If I understand correctly, you use vim on terminal on both OSes, right? To use the latest Vim available on homebrew, you should run
not MacVim. The latest version in HEAD is 7.4.537. |
That's what I've done to test it. Both MacVim terminal and vim have same behavior. |
But your Vim version shows 7.4.383. That is where I am confused. |
That was the version for MacVim. As I said, afterwards I've uninstalled it and installed vim from HEAD of official mercurial repositories through homebrew just to test its behavior, which was the same. |
This is the version in homebrew's cache (since I have uninstalled it):
|
Ah, now, that I've actually run some code with let g:SingleCompile_showquickfixiferror = 1
let g:SingleCompile_showquickfixifwarning = 1 I'm also experiencing the code buffer showing up in-place of the quickfix window. Just like @lookforit's screenshot. |
@oblitum Sorry that it seems I really can't do anything to help. This seems to be different behavior on different OSes of Vim (same code produces different output), we have to extract the problematic code and report it back to Vim. I'll try if I can. |
Here is my setting related to
SingleCompile
The weired thing is ,when
SingleCompileRun
executed,the quickfix window shows the result automatically,also and a new source code buffer open horizontally .How to disable this new -open buffer?
The text was updated successfully, but these errors were encountered: