-
Notifications
You must be signed in to change notification settings - Fork 34
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
Conflicts with neomake #44
Comments
There's currently no attempt on either side to communicate with the other plugin. That would be a nightmare without a proper plugin API. Anyway, I'll take a look at this issue ASAP. |
I've installed Neomake but now I'd like to see your settings for both Neomake and vim-qf in order to reproduce your context as faithfully as possible. |
The following settings result in neomake opening the loclist on write, regardless of the fact that auto-opening the loclist is disabled in vim-qf.
Conversely, if you try the following settings:
The loclist still gets opened on write, even though |
It looks like both plugins have overlapping features, which makes sense because both plugins are heavily quickfix-oriented. I can see three directions to take:
I will certainly not take direction #2 and I doubt Neomake's author will take direction #3 so it looks like we are left with direction #1. I think I will simply add a disclaimer in Sorry, but this is a WONTFIX issue. |
Yes, that's fair enough. I had already taken direction 1 by myself, I mainly wanted to make sure I wasn't missing an obvious solution to the problem. Thank you for looking into this! |
It seems like the annoying part with |
I don't know how much of this can be adressed on the vim-qf side, but there are some issues when vim-qf and neomake are used together.
If vim-qf is used out of the box without any configuration, the config option
let g:neomake_open_list
has no effect on the loclist opened by neomake regardless of what value it is set to. It appears that the behaviour of the loclist is overwritten by vim-qf.If I set
let g:qf_auto_open_loclist = 0
, this does not prevent neomake from opening a loclist as you would expect, but it does allow neomake to bypass vim-qf for the loclist settings, meaningneomake_open_list
settings now take effect.However, some vim-qf settings and function calls, such as
qf_window_bottom
orqf_loc_toggle_stay
still retain control over the neomake loclist.So in effect, the communication between vim-qf and neomake does not work as one would intuitively expect; some, but not all of the settings do not transfer between the two.
The text was updated successfully, but these errors were encountered: