Closed zipy124 closed 3 months ago
I merged and changed lsp-pyright-fork
to lsp-pyright-langserver-command
. Thanks!
I merged and change
lsp-pyright-fork
tolsp-pyright-langserver-command
. Thanks!
Thank you for the quick review, changes and merge!
Overall it looks good, except
lsp-pyright-fork
option. I am afraid it's confusing. And, are all options and arguments ofpyright
andbasedpyright
just same?
Of the options provided by this module they are all the same (I think). I have unfortunately run into the fact that the options are not all the same for the full list, for example:
python.analysis.typeCheckingMode vs basedpyright.analysis.typeCheckingMode
and further confusing matters:
basedpyright.analysis.useLibraryCodeForTypes vs python.analysis.useLibraryCodeForTypes or pyright.useLibraryCodeForTypes .
I'm unsure what the best option is here between the available options:
Well, it's better keep the common configurations and leave the rest to the json file, IMO.
This PR addresses issue: #92
All commands that use "pyright/" are now instead created via concatenating the fork with the command. This can be customised with the lsp-pyright-fork customizable option.
use of "backquote" command instead of " ' " is because of an emacs-lisp bug please see: https://stackoverflow.com/questions/17394638/nesting-backquote-and-in-emacs-lisp and https://mail.gnu.org/archive/html/bug-gnu-emacs/2023-02/msg00617.html
All suggestions welcome, this is my first time contributing emacs-lisp code so I am not well versed with the standard practices :)