From: Tim Johnson <thjmmj15@gmail.com>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: MLEmacs <Help-gnu-emacs@gnu.org>
Subject: Re: Tips for upgrading emacs
Date: Tue, 31 Oct 2023 09:13:14 -0800 [thread overview]
Message-ID: <b4375de4-27ab-4410-b526-34bb62abacf0@gmail.com> (raw)
In-Reply-To: <87pm0vh416.jnqunsglt@vorpgeoj.ndrditop.info>
On 10/30/23 7:19 PM, Bob Newell wrote:
>> 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.
>
Thanks Bob. Drew Adams offers the following advice in his
help-fns+ package:
;; Note: As of Emacs 24.4, byte-compiling this file in one Emacs
;; version and using the compiled file in another Emacs version
;; does not work.
Forgetting his advice has caused me headaches.
Would it be reasonable to run byte-compile against all installed packages
after an upgrade?
cheers
--
Tim
thjmmj15@gmail.com
next prev parent reply other threads:[~2023-10-31 17:13 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
2023-10-31 17:13 ` Tim Johnson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4375de4-27ab-4410-b526-34bb62abacf0@gmail.com \
--to=thjmmj15@gmail.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=bobnewell@bobnewell.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.