From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Preloading xwidget.el on xwidget builds?
Date: Wed, 15 Dec 2021 23:50:04 -0500 [thread overview]
Message-ID: <jwvy24lkvfb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o85hma9k.fsf@yahoo.com> (Po Lu's message of "Thu, 16 Dec 2021 12:41:43 +0800")
>>> xwidget.el defines various parts of the internal xwidget machinery, such
>>> as the `xwidget-event' handler, and pieces of Lisp code that keep
>>> xwidget display working correctly.
>>>
>>> Using xwidget-related C functions without xwidget.el loaded can lead to
>>> crashes and display problems, so I propose to preload that file on
>>> xwidget builds.
>>
>> IME files that are preloaded in some config and not on others are
>> a source of trouble. I'd rather we fix this some other way, e.g. by
>> autoloading those function.
>
> How would autoloading solve that problem though: `make-xwidget' and such
> are defined in C code, but their display depends on xwidget.el to work
> correctly.
Depends on details I don't know, but presumably `make-xwidget` could
explicitly require/load `xwidget.el`. Or the display could end up
loading `xwidget.el` when it calls a function defined there in (by
marking those functions as autoloaded).
Stefan
next prev parent reply other threads:[~2021-12-16 4:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8zpml5d.fsf.ref@yahoo.com>
2021-12-16 0:46 ` Preloading xwidget.el on xwidget builds? Po Lu
2021-12-16 4:33 ` Stefan Monnier
2021-12-16 4:41 ` Po Lu
2021-12-16 4:50 ` Stefan Monnier [this message]
2021-12-16 4:51 ` Stefan Monnier
2021-12-16 4:52 ` Po Lu
2021-12-16 5:06 ` Lars Ingebrigtsen
2021-12-16 5:10 ` Po Lu
2021-12-16 5:46 ` Lars Ingebrigtsen
2021-12-16 7:46 ` Eli Zaretskii
2021-12-16 7:54 ` Po Lu
2021-12-16 7:39 ` Eli Zaretskii
2021-12-16 7:47 ` Po Lu
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=jwvy24lkvfb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).