Marc Reisner
Marc Reisner
Looks like this has something to do with how %INC gets set. ``` [mreisner@vm-mreisner mre]$ perl -MData::Dumper -I. -e 'BEGIN { require "/home/mreisner/mre/Test3.pm"; print Dumper \%INC }' this should only...
I plan on merging this when I'm confident that there are no more issues, probably next week.
This has worked for me - merging.
@c-alpha Thanks for submitting this. I just have a couple of questions.
@c-alpha I updated the settings - they now start with `pls.` (not `perl.pls`). Ready for you to make the PR on the emacs side of things. Thanks!
That's how configuration is sent. It's not included in `initialize`, you need to request the config from the server with a `workspace/configuration` request. We should be requesting both `perl` and...
I don't think initializationOptions is the correct thing to use here. ```typescript /** * User provided initialization options. */ initializationOptions?: LSPAny ``` The way it should work is: 1. The...
To be 100% clear - yes, workspace/didChangeConfiguration sends a settings parameter. However, in practice, the client is not required to actually include any settings in it. VSCode just sends a...
Okay, looks good.
I noticed that `pls.syntax.args` was not included in your PR. It's a newer option, not likely to be used, but we should probably still include it.