Both today and yesterday I wished to know which version of perlnavigator was actually being run, but could not figure out how to make it tell me. I tried running perlnavigator --version, but that only throws a long error about the 'Connection input stream' something. The same is true for running perlnavigator with -V, --help or -h.
Does adding some or all of those options seem like a reasonable feature for perlnavigator to have? Unfortunately I'm lost with typescript, so I'm not attempting a patch.
When not being able to verify to be running the correct version using the command line, I looked at the LSP communication. The response perlnavigator is giving to an 'initialize' method call is:
{
"jsonrpc": "2.0",
"id": 2,
"result": {
"capabilities": {
"textDocumentSync": 2,
"completionProvider": {
"resolveProvider": true,
"triggerCharacters": [
"$",
"@",
"%",
"-",
">",
":"
]
},
"definitionProvider": true,
"documentSymbolProvider": true,
"workspaceSymbolProvider": true,
"hoverProvider": true,
"documentFormattingProvider": true,
"documentRangeFormattingProvider": true,
"signatureHelpProvider": {
"triggerCharacters": [
"(",
",",
")"
]
}
}
}
}Other LSP:s tend to include a serverInfo block inside of result:
"serverInfo": {
"name": "pylsp",
"version": "1.12.2"
}
…
"serverInfo": {
"name": "rust-analyzer",
"version": "2025.06.23"
}
…
"serverInfo": {
"name": "Tombi LSP",
"version": "0.5.3"
}Would it be desirable to have perlnavigator to also do that?
Both today and yesterday I wished to know which version of perlnavigator was actually being run, but could not figure out how to make it tell me. I tried running
perlnavigator --version, but that only throws a long error about the 'Connection input stream' something. The same is true for running perlnavigator with-V,--helpor-h.Does adding some or all of those options seem like a reasonable feature for perlnavigator to have? Unfortunately I'm lost with typescript, so I'm not attempting a patch.
When not being able to verify to be running the correct version using the command line, I looked at the LSP communication. The response perlnavigator is giving to an 'initialize' method call is:
{ "jsonrpc": "2.0", "id": 2, "result": { "capabilities": { "textDocumentSync": 2, "completionProvider": { "resolveProvider": true, "triggerCharacters": [ "$", "@", "%", "-", ">", ":" ] }, "definitionProvider": true, "documentSymbolProvider": true, "workspaceSymbolProvider": true, "hoverProvider": true, "documentFormattingProvider": true, "documentRangeFormattingProvider": true, "signatureHelpProvider": { "triggerCharacters": [ "(", ",", ")" ] } } } }Other LSP:s tend to include a serverInfo block inside of result:
Would it be desirable to have perlnavigator to also do that?