You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using neomake with the automake function, really like it. It strikes a nice balance between flexible, and sensible for common cases.
I really like most of the "outputs" of linting in response to automake (virtual text, signs), but I don't like the automake overriding the location list. If I have something else loaded into the location list (e.g. a stacktrace) then I want to keep it there even while I edit/navigate code.
On the other hand, if the last thing in the location list is the output from Neomake, I'm happy for it to be updated as I make changes.
When I type :Neomake, I want the location list to update regardless of contents.
The text was updated successfully, but these errors were encountered:
To achieve what you propose, Neomake needs a way to cooperate with other plugins that also use location lists, because the location list of a window is a shared resource. I don't think vim provides a mechanism to allow a plugin to use a location list exclusively. Even if it does, it will be a bad idea for a single misbehaving plugin that fails to release its ownership to a location list would cause other plugins to stop functioning.
I'm using neomake with the automake function, really like it. It strikes a nice balance between flexible, and sensible for common cases.
I really like most of the "outputs" of linting in response to automake (virtual text, signs), but I don't like the automake overriding the location list. If I have something else loaded into the location list (e.g. a stacktrace) then I want to keep it there even while I edit/navigate code.
On the other hand, if the last thing in the location list is the output from Neomake, I'm happy for it to be updated as I make changes.
When I type
:Neomake
, I want the location list to update regardless of contents.The text was updated successfully, but these errors were encountered: