Skip to content
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

Feature proposal: drop quickfix feedback #31

Open
mjacobus opened this issue Mar 17, 2015 · 4 comments
Open

Feature proposal: drop quickfix feedback #31

mjacobus opened this issue Mar 17, 2015 · 4 comments

Comments

@mjacobus
Copy link

Hey folks!
First of all thank you for this awesome plugin. It helps me a lot!

Secondly, I would like to make a change proposal:

Instead of using the quickfix to display the errors, the errors could be displayed like in syntastic plugin:

  1. When the cursor is on a line containing an error, the error message is echoed in the command
    window.

The problem with the quickfix is that when we are using splits it is hard to read code or the QA errors. So the syntastic approach is much less invasive, IMHO.

Of course, probably some people find the quickfix better, so perhaps it could be optional. I would love to work on that, if you find that interesting, but I would have first to learn how to be a vim-script ninja.

Cheers!

@joonty
Copy link
Owner

joonty commented Aug 25, 2015

Hi @mjacobus,

Sorry for the long delay in getting back to you. It's just me maintaining this plugin at the moment, and I've pretty much taken a break from OSS development for the last year! I also don't really use PHP much any more, which makes it doubly hard to keep this plugin up-to-date. Fortunately, there are plenty of people who are contributing to it.

I agree with your idea of making it optional as to whether you want to use quickfix or the syntastic approach. But considering the above, I don't think I'd have time to develop it - if you're still interested in putting the time in then a PR would be very welcome, and I'd be more than happy to test it.

Thanks

@mjacobus
Copy link
Author

Hy @joonty

Thank you for your response. Yeah, I get it, it is not easy to maintain a Open Source project.
I think I did try to understand the code and come up with a PR, but my vimL skills are terrible.

If I find the time to get deeper to the point I can contribute with that PR you will see it here. ;)

Thank you so much for the very fine job you've done with this plugin =)

@wildtron
Copy link

wildtron commented Mar 9, 2016

@joonty Any plans with this? :D

@joonty
Copy link
Owner

joonty commented Mar 11, 2016

Hi @wildtron, probably not to be honest, for the reasons I mentioned in my first response. I'm focusing most of my energy on Vdebug, and even that's not getting much attention! As I say, I'm happy to accept pull requests, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants