-
Notifications
You must be signed in to change notification settings - Fork 2
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
ST4: SublimeLinter: WARNING: perl: Defining 'cls.executable' has no effect. Please cleanup and remove this setting. #14
Comments
I no longer use this linter, but I would be happy to merge a fix. I assume it would look similar to oschwald/SublimeLinter-perlcritic#9. |
Huh. Strange. Both perl and perllinter give errors (yeah, these cls.executable) installed from Package Control DB, but when I put master branches (raw code) it's gone. @oschwald does this mean this is also solved in this as well as in perllinter, just both are not updated to Package Control DB? I thought to do PR but seems in masters there nothing to fix :) Please advise. |
I no longer use Sublime and this code isn't maintained anymore. I suspect you would have a much better experience using Perl Naviagor with a Sublime LSP client. This is what I do in my current editor of choice. |
Alright, I'll tell Sublime people around me here to switch, we have some. @oschwald - btw side question in vscode context: does bscan.perlnavigator coexists well with richterger.perl or overlaps? |
I don't use vscode, but I think you would generally use Perl Navigator or |
it's non-trivial to configure both (also I tried PLS) for Sublime Text ... Bumping some time @oschwald so you have it for ST4? Any hints on how to config? I gave up on the others two: |
I have just upgraded to ST4 and I get the following warning in the console:
SublimeLinter: WARNING: perl: Defining 'cls.executable' has no effect. Please cleanup and remove this setting.
Could you fix this please? Thanks! 😉
The text was updated successfully, but these errors were encountered: