From: David Masterson <dsmasterson@gmail.com>
To: Joel Reicher <joel.reicher@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Dealing with a system Emacs properly
Date: Sun, 14 Jul 2024 10:57:46 -0700 [thread overview]
Message-ID: <LV8P223MB09209807C00B5556573CFC55A2A02@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <86msmk1piy.fsf@gmail.com> (Joel Reicher's message of "Sun, 14 Jul 2024 16:00:37 +1000")
Joel Reicher <joel.reicher@gmail.com> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>> Joel Reicher <joel.reicher@gmail.com> writes:
>>
>>> David Masterson <dsmasterson@gmail.com> writes:
>>>
>> I have the package auto-package-update which regularly checks my
>> packages for updates on [M]Elpa.
>
> I don't use that anymore, but I can see it draws on both package-alist
> and package--builtins so I'd expect it to work for upgrading builtins
> also. Can you check the values of those variables if the issue is
> still happening or happens again?
Hmm. I see Org-9.5.5 in package--builtins even after I removed it from
/usr/share/emacs/elpa (well, hid it in /usr/share/emacs) to try to see
to see if I could local install Org-9.7.6 (which seemed to work). How
did package--builtins find 9.5.5 ?!?
>>> The latter is normal behaviour for builtin packages...
>>
>> Latter? I don't see package-upgrade-all in describe-function.
>
> Possibly it's not in the version you have?
>
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Package-Installation.html#index-package_002dupgrade
Ah, yeah. The manual your pointing to is for Emacs 29.2 while I'm at
28.2. I'll have to look at Debian backports to see if I can install an
Emacs v29 in bookworm. Building Emacs from scratch myself winds up
loading too many dependent system software which overloads my small
diskspace on my Chromebook.
>> Okay, by shadow you mean cover. Most of the time, that's true. Once
>> in awhile, there's some problem.
>
> Could you provide specifics? I believe redefinition and overriding (of
> anything!) should always be possible in Emacs.
Don't remember the specifics, but I believe it had something to with
org-compat.el and that the builtin org-compat was being loaded before
the new Org was loaded and, therefore, interfered with the load of the
new Org. Org-compat is supposed to avoid this, but an update to Org
broke it. My hack was to remove the old Org instead of waiting for the
fix.
--
David Masterson
next prev parent reply other threads:[~2024-07-14 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 4:53 Dealing with a system Emacs properly David Masterson
2024-07-13 6:16 ` Joel Reicher
2024-07-14 5:18 ` David Masterson
2024-07-14 6:00 ` Joel Reicher
2024-07-14 17:57 ` David Masterson [this message]
2024-07-13 7:11 ` Michel Verdier
2024-07-14 5:20 ` David Masterson
2024-07-14 7:39 ` Michel Verdier
2024-07-14 17:58 ` David Masterson
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=LV8P223MB09209807C00B5556573CFC55A2A02@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=joel.reicher@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).