Avoid quickfix override

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Avoid quickfix override

Cristo García
I use linters (plugins like ALE), which use the quickfix window every time I enter a buffer or every time I edit the text, when I compile my program and I get a list of warnings and/or errors and I jump to one of them the quickfix get overrode by the linter plugin.

I know I can use :colder, :cnewer and :chistory, the problem is that sometimes the quickfix with the info of the compiler get wipe out when I do enough jumps and not to mention that it's too tedious being all the time switching between quickfix.

For now my idea is to turn off the quickfix every time I compile and turn it back with a command or a map when I am finish, but this is obviously a workaround.

Does someone of you got a better idea?, It would be great if the artist plugin has access to one instance of the quickfix and only his plugin can override that instance or give the user the possibility of locking one quickfix so when you open the quickfix window you always see the one you locked and make sure it doesn't get override.  

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/74a7f81d-d252-4261-ad46-9bb57d819d7fn%40googlegroups.com.