emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

emacs-29 af43f0a2954 1/2: * doc/misc/erc.texi: Elaborate on upgrading vi


From: F. Jason Park
Subject: emacs-29 af43f0a2954 1/2: * doc/misc/erc.texi: Elaborate on upgrading via ELPA.
Date: Wed, 26 Apr 2023 09:46:11 -0400 (EDT)

branch: emacs-29
commit af43f0a2954f4a4e735a6e3d159edc3392eaeb6c
Author: F. Jason Park <jp@neverwas.me>
Commit: F. Jason Park <jp@neverwas.me>

    * doc/misc/erc.texi: Elaborate on upgrading via ELPA.
---
 doc/misc/erc.texi | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/doc/misc/erc.texi b/doc/misc/erc.texi
index b80affbc954..ad30546c9d5 100644
--- a/doc/misc/erc.texi
+++ b/doc/misc/erc.texi
@@ -1477,10 +1477,30 @@ questions.  You can also try the relatively quiet 
@samp{#erc}, on the
 same network, for more involved questions.
 
 @item
+@anchor{Upgrading}
 You can check GNU ELPA between Emacs releases to see if a newer
 version is available that might contain a fix for your issue:
 @uref{https://elpa.gnu.org/packages/erc.html}.
 
+To upgrade, run @kbd{M-x list-packages @key{RET}}.  In the
+@file{*Packages*} (@code{package-menu-mode}) buffer, click the
+@samp{erc} package link for the desired version.  If unsure, or if the
+version column is too narrow to tell, try the bottom-most candidate.
+In the resulting @code{help-mode} buffer, confirm the version and
+click @samp{Install}.  Make sure to restart Emacs before reconnecting
+to IRC, and don't forget that you can roll back to the previous
+version by running @kbd{M-x package-delete @key{RET}}.
+@xref{Packages,,,emacs, the Emacs manual} for more information.
+
+In the rare instance you need an emergency fix or have volunteered to
+test an edge feature between ERC releases, you can try adding
+@samp{("devel" . "https://elpa.gnu.org/devel/";)} to
+@code{package-archives} prior to performing the steps above.  For
+this, you'll want to instead select a ``snapshot'' version from the
+menu.  Please be aware that when going this route, the latest changes
+may not yet be available and you run the risk of incurring other bugs
+and encountering unstable features.
+
 @item
 To report a bug in ERC, use @kbd{M-x erc-bug}.
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]