From: Bob Newell <bobnewell@bobnewell.net>
To: Tim Johnson <thjmmj15@gmail.com>
Cc: MLEmacs <Help-gnu-emacs@gnu.org>
Subject: Re: Tips for upgrading emacs
Date: Mon, 30 Oct 2023 17:19:49 -1000 [thread overview]
Message-ID: <87pm0vh416.jnqunsglt@vorpgeoj.ndrditop.info> (raw)
In-Reply-To: <1db41a97-507d-4556-90b4-0a2567774b77@gmail.com> (Tim Johnson's message of "Mon, 30 Oct 2023 15:27:04 -0800")
> Can others reading this contribute any tips for things to do after
> upgrading emacs?
The one and only "must do" that I've found is to go to
/usr/share/emacs/29.1/lisp (substitute new version for 29.1)
and 'sudo rm -Rf org'.
This is because I get the latest org from the package manager
and having a mixed installation is a problem. So this is not
required if you just want to use the org version as delivered
with the new emacs version.
Generally if you keep your elisp packages up to date you
shouldn't have a problem. Even then, elisp is backward
compatible. I'm sure there are edge cases and exceptions but
I've never had to do much of anything when upgrading emacs,
which in any case for me is not frequent as I don't stay
bleeding edge.
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2023-10-31 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 23:27 Tips for upgrading emacs Tim Johnson
2023-10-31 3:19 ` Bob Newell [this message]
2023-10-31 17:13 ` Tim Johnson
2023-10-31 22:04 ` Gregor Zattler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm0vh416.jnqunsglt@vorpgeoj.ndrditop.info \
--to=bobnewell@bobnewell.net \
--cc=Help-gnu-emacs@gnu.org \
--cc=thjmmj15@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).