You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lsp-php.el , in lsp-serenata-init-options sends the config settings in a group labelled "config", but Serenata expects it to be labelled "configuration", so per-project configuration never works.
Versions:
lsp-mode: master and 20201011.1353
Serenata: master and 5.4.0
I verified this by creating a .dir-locals.el file in my project repo, adding the hack-local-variables hook, doing M-x debug-entry for lsp, and seeing the following sent:
I then edited lsp-php.el locally to change the string to ":configuration", closed and restarted emacs with a php file from the project repo, and then Serenata re-indexed the project, writing the sqlite project index file into my specified location. Previously it had written the file into /tmp, which is the behavior when Serenata has no configuration information passed to it.
The text was updated successfully, but these errors were encountered:
lsp-php.el , in lsp-serenata-init-options sends the config settings in a group labelled "config", but Serenata expects it to be labelled "configuration", so per-project configuration never works.
Versions:
I verified this by creating a .dir-locals.el file in my project repo, adding the hack-local-variables hook, doing M-x debug-entry for lsp, and seeing the following sent:
But I got the following error message from Serenata:
Digging around in Serenata, one finds the following:
https://gitlab.com/Serenata/Serenata/-/blob/master/src/UserInterface/JsonRpcQueueItemHandler/InitializeJsonRpcQueueItemHandler.php#L180
I then edited lsp-php.el locally to change the string to ":configuration", closed and restarted emacs with a php file from the project repo, and then Serenata re-indexed the project, writing the sqlite project index file into my specified location. Previously it had written the file into /tmp, which is the behavior when Serenata has no configuration information passed to it.
The text was updated successfully, but these errors were encountered: