mirror of
https://github.com/masscollaborationlabs/emacs.git
synced 2025-07-18 18:00:11 +00:00
; Prefer "language server" to "LSP server" in Eglot manual
* eglot.texi (Quick Start, Customizing Eglot) (Project-specific configuration) (Troubleshooting Eglot): LSP server -> language server.
This commit is contained in:
parent
94a21c8864
commit
013057e351
1 changed files with 17 additions and 15 deletions
|
@ -154,11 +154,11 @@ Use Eglot.
|
||||||
|
|
||||||
Most Eglot facilities are integrated into Emacs features, such as
|
Most Eglot facilities are integrated into Emacs features, such as
|
||||||
ElDoc, Flymake, Xref, and Imenu. However, Eglot also provides
|
ElDoc, Flymake, Xref, and Imenu. However, Eglot also provides
|
||||||
commands of its own, mainly to perform tasks by the LSP server, such
|
commands of its own, mainly to perform tasks by the language server,
|
||||||
as @kbd{M-x eglot-rename} (to rename an identifier across the entire
|
such as @kbd{M-x eglot-rename} (to rename an identifier across the
|
||||||
project), @kbd{M-x eglot-format} (to reformat and reindent code), and
|
entire project), @kbd{M-x eglot-format} (to reformat and reindent
|
||||||
some others. @xref{Eglot Commands}, for the detailed list of Eglot
|
code), and some others. @xref{Eglot Commands}, for the detailed list
|
||||||
commands.
|
of Eglot commands.
|
||||||
|
|
||||||
@item
|
@item
|
||||||
That's it!
|
That's it!
|
||||||
|
@ -968,7 +968,7 @@ mechanism.
|
||||||
@cindex progress
|
@cindex progress
|
||||||
@item eglot-report-progress
|
@item eglot-report-progress
|
||||||
Set this variable to true if you'd like progress notifications coming
|
Set this variable to true if you'd like progress notifications coming
|
||||||
from the LSP server to be handled as Emacs's progress reporting
|
from the language server to be handled as Emacs's progress reporting
|
||||||
facilities.
|
facilities.
|
||||||
@end table
|
@end table
|
||||||
|
|
||||||
|
@ -1079,10 +1079,11 @@ plists. Some examples are useful.
|
||||||
|
|
||||||
Let's say you want to configure two language servers to be used in a
|
Let's say you want to configure two language servers to be used in a
|
||||||
project written in a combination of the Python and Go languages. You
|
project written in a combination of the Python and Go languages. You
|
||||||
want to use the @command{pylsp} and @command{gopls} LSP servers. In
|
want to use the @command{pylsp} and @command{gopls} languages
|
||||||
the documentation of the servers in question (or in some other editor's
|
servers. In the documentation of the servers in question (or in some
|
||||||
configuration file, or in some blog article), you find the following
|
other editor's configuration file, or in some blog article), you find
|
||||||
configuration options in informal dotted-notation syntax:
|
the following configuration options in informal dotted-notation
|
||||||
|
syntax:
|
||||||
|
|
||||||
@example
|
@example
|
||||||
pylsp.plugins.jedi_completion.include_params: true
|
pylsp.plugins.jedi_completion.include_params: true
|
||||||
|
@ -1300,13 +1301,14 @@ slowly, try to customize the variable @code{eglot-events-buffer-size}
|
||||||
(@pxref{Eglot Variables}) to 0. This will disable any debug logging
|
(@pxref{Eglot Variables}) to 0. This will disable any debug logging
|
||||||
and may speed things up.
|
and may speed things up.
|
||||||
|
|
||||||
In other situations, the cause of poor performance lies in the LSP
|
In other situations, the cause of poor performance lies in the
|
||||||
server itself. Servers use aggressive caching and other techniques to
|
language server itself. Servers use aggressive caching and other
|
||||||
improve their performance. Often, this can be tweaked by changing the
|
techniques to improve their performance. Often, this can be tweaked
|
||||||
server configuration (@pxref{Advanced server configuration}).
|
by changing the server configuration (@pxref{Advanced server
|
||||||
|
configuration}).
|
||||||
|
|
||||||
If you think you have found a bug, we want to hear about it. Before
|
If you think you have found a bug, we want to hear about it. Before
|
||||||
reporting a bug, keep in mind that interaction with LSP servers
|
reporting a bug, keep in mind that interaction with language servers
|
||||||
represents a large quantity of unknown variables. Therefore, it is
|
represents a large quantity of unknown variables. Therefore, it is
|
||||||
generally both @emph{difficult} and @emph{absolutely essential} that
|
generally both @emph{difficult} and @emph{absolutely essential} that
|
||||||
the maintainers reproduce bugs exactly as they happened to you, the
|
the maintainers reproduce bugs exactly as they happened to you, the
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue