From f965f35b33b7d722b34796823012dcd2a06ae0bd Mon Sep 17 00:00:00 2001 From: Dmitry Gutov Date: Mon, 24 Apr 2023 02:00:54 +0300 Subject: Rename all functions called package-*-update-* to package-*-upgrade-* * lisp/emacs-lisp/package-vc.el (package-vc-upgrade-all): Rename from 'package-vc-update-all'. (package-vc-upgrade): Rename from 'package-vc-update'. * lisp/emacs-lisp/package.el (package-upgrade): Rename from 'package-update' (bug#62750). (package--upgradeable-packages): Rename from 'package--updateable-packages'. (package-upgrade-all): Rename from 'package-update-all'. --- doc/emacs/package.texi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi index 2b03399b0a7..d1766026db2 100644 --- a/doc/emacs/package.texi +++ b/doc/emacs/package.texi @@ -329,15 +329,15 @@ version of the package, a newer version is also installed. @section Package Installation @findex package-install -@findex package-update -@findex package-update-all +@findex package-upgrade +@findex package-upgrade-all Packages are most conveniently installed using the package menu (@pxref{Package Menu}), but you can also use the command @kbd{M-x package-install}. This prompts for the name of a package with the @samp{available} status, then downloads and installs it. Similarly, -if you want to update a package, you can use the @kbd{M-x -package-update} command, and if you just want to update all the -packages, you can use the @kbd{M-x package-update-all} command. +if you want to upgrade a package, you can use the @kbd{M-x +package-upgrade} command, and if you want to upgrade all the packages, +you can use the @kbd{M-x package-upgrade-all} command. @cindex package requirements A package may @dfn{require} certain other packages to be installed, @@ -551,8 +551,8 @@ bugs. source code for a package directly from source. The command will also automatically ensure that all files are byte-compiled and auto-loaded, just like with a regular package. Packages installed this way behave -just like any other package. You can update them using -@code{package-update} or @code{package-update-all} and delete them +just like any other package. You can upgrade them using +@code{package-upgrade} or @code{package-upgrade-all} and delete them again using @code{package-delete}. They are even displayed in the regular package listing. If you just wish to clone the source of a package, without adding it to the package list, use -- cgit v1.2.1 From 44ebd9cbd56b820ad5b014b442b5a9142e8cac89 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20T=C3=A1vora?= Date: Thu, 27 Apr 2023 21:08:17 +0100 Subject: Eglot: explain how to update Eglot in manual (bug#62720) * lisp/progmodes/eglot.el (eglot-update): New command. * doc/misc/eglot.texi (Troubleshooting): Rework. --- doc/misc/eglot.texi | 32 +++++++++++++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/misc/eglot.texi b/doc/misc/eglot.texi index fc5449b0e8d..4599b78ba56 100644 --- a/doc/misc/eglot.texi +++ b/doc/misc/eglot.texi @@ -1265,7 +1265,7 @@ is serialized by Eglot to the following JSON text: @chapter Troubleshooting Eglot @cindex troubleshooting Eglot -This section documents commands and variables that can be used to +This chapter documents commands and variables that can be used to troubleshoot Eglot problems. It also provides guidelines for reporting Eglot bugs in a way that facilitates their resolution. @@ -1275,6 +1275,8 @@ pop up special buffers that can be used to inspect the communications between the Eglot and language server. In many cases, this will indicate the problems or at least provide a hint. +@node Performance +@section Performance @cindex performance A common and easy-to-fix cause of performance problems is the length of the Eglot events buffer because it represent additional work that @@ -1289,6 +1291,30 @@ techniques to improve their performance. Often, this can be tweaked by changing the server configuration (@pxref{Advanced server configuration}). +@node Getting the latest version +@section Getting the latest version +@cindex updating Eglot + +To install the latest Eglot on an Emacs version that does not bundle +Eglot, use @kbd{M-x package-install}. + +Often, a newer Eglot version exists that has fixed a longstanding bug, +has more LSP features, or just better support for a particular +language server. Recent Eglot versions can self-update via the +command @kbd{M-x eglot-update}. This will replace any currently +installed version with the newest one available from the ELPA archives +configured in @code{package-archives}. + +You may update though other methods, such as @code{package-install}, +@code{use-package}, @code{list-packages} or the newer +@code{package-update}. However, do read the docstrings of these +commands, as some may not work in exactly the same way across Emacs +versions, meaning your configuration may be not portable. + +@node Reporting bugs +@section Reporting bugs +@cindex bug reports + If you think you have found a bug, we want to hear about it. Before reporting a bug, keep in mind that interaction with language servers represents a large quantity of unknown variables. Therefore, it is @@ -1332,6 +1358,10 @@ public Git repository. Include versions of the software used. The Emacs version can be obtained with @kbd{M-x emacs-version}. +We welcome bug reports about all Eglot versions, but it is helpful to +first check if the problem isn't already fixed in the latest version +(@pxref{Getting the latest version}). + It's also essential to include the version of ELPA packages that are explicitly or implicitly loaded. The optional but popular Company or Markdown packages are distributed as GNU ELPA packages, not to mention -- cgit v1.2.1