From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el
Date: Wed, 5 Apr 2023 18:41:06 +0700 [thread overview]
Message-ID: <u0jmoj$9cv$1@ciao.gmane.io> (raw)
In-Reply-To: <87mt3nai7z.fsf@localhost>
Ihor, I am sorry, but I sent this message off-list at first.
On 04/04/2023 20:29, Ihor Radchenko wrote:
>
> Sure. Anything Emacs devs can act on. If you can prove that the problem
> is in Emacs source code, we can report it in
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59882 and let Emacs devs
> fix things.
I do not expect any result that may be useful for Emacs dev. I hope, the
code added to emacs-29 branch fixes the issue. Outcome may be helpful
for choosing better variant of `org-assert-version' and for demystifying
causes why you can not reproduce it in gentoo.
> This looks like
> https://orgmode.org/list/jwvsfkv5s7l.fsf-monnier+emacs@gnu.org
I have not looked into make rules used in Emacs source tree, but I
expect it is another issue. I do not like that elisp can not generate
list of dependencies during compilation similar to "gcc -MD". Otherwise
I do not see a way to implement incremental rebuild if stale .elc files
are preferred to updated .el sources by `require'.
> But Emacs >26 + package-install specifically arranges unloading the
> older version of the library.
What changes are you writing about? I mean
`package--reload-previously-loaded'
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59882#71
9dfd945a2c2 2021-11-07 01:28:47 +0100 dickmao: Fix byte compilation of
package built-ins
and I do not see similar changes even in Emacs-28.
next prev parent reply other threads:[~2023-04-05 11:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 7:26 [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el Bastien
2022-12-02 3:38 ` Kyle Meyer
2022-12-02 7:44 ` Bastien
2022-12-03 4:18 ` Kyle Meyer
2022-12-06 3:54 ` David Masterson
2022-12-06 5:44 ` tomas
2022-12-06 7:13 ` David Masterson
2022-12-07 11:43 ` Ihor Radchenko
2022-12-07 14:08 ` Max Nikulin
2023-03-29 13:38 ` Ihor Radchenko
2023-03-29 16:04 ` Max Nikulin
2023-03-29 16:52 ` Ihor Radchenko
2023-04-01 14:44 ` Max Nikulin
2023-04-02 8:35 ` Ihor Radchenko
2023-04-02 15:59 ` Max Nikulin
2023-04-02 16:44 ` Ihor Radchenko
2023-04-04 12:08 ` Max Nikulin
2023-04-04 13:29 ` Ihor Radchenko
2023-04-05 11:41 ` Max Nikulin [this message]
2023-04-08 16:47 ` Max Nikulin
2023-04-09 8:29 ` Ihor Radchenko
2023-04-10 6:13 ` Max Nikulin
2023-04-10 16:58 ` Ihor Radchenko
2023-06-04 10:58 ` Max Nikulin
2022-12-06 3:00 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='u0jmoj$9cv$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).