unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: luangruo@yahoo.com
Cc: bobodeangelis@gmail.com, 74295@debbugs.gnu.org
Subject: bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support
Date: Sat, 30 Nov 2024 11:46:19 +0200	[thread overview]
Message-ID: <86bjxx9hqs.fsf@gnu.org> (raw)
In-Reply-To: <865xoqkywy.fsf@gnu.org> (message from Eli Zaretskii on Thu, 14 Nov 2024 10:22:21 +0200)

Ping!

> Cc: 74295@debbugs.gnu.org
> Date: Thu, 14 Nov 2024 10:22:21 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Andrew De Angelis <bobodeangelis@gmail.com>
> > Date: Sun, 10 Nov 2024 10:13:17 -0500
> > 
> > I have a question and a possible patch to contribute.
> > For context: the most glaring issues with xwidget support of NS have been fixed: I contributed a patch to get
> > rid of memory leaks a while ago, under: "bug#60703 Patches to xwidget code".
> > 
> > I've just noticed that I forgot to update the TODO file, so it still mentions crashes:
> > > trying to display a xwidget in the "killed" state will make Emacs crash.
> > 
> > I've used the xwidget feature extensively and in my experience, xwidgets do not crash Emacs anymore.
> > 
> > Question:
> >  - Could someone clarify what we mean by displaying a xwidget in the "killed" state? I want to make sure I
> > understand the problem and it's fixed
> 
> Can someone who knows about this (Po Lu?) answer Andrew's question?
> 
> > Possible patch (if the problem is indeed fixed):
> > Attached. Remove the mention of crashes, and clarify which features are still missing from the NS port.
> 
> I installed that on the emacs-30 release branch, thanks.
> 
> 
> 
> 





  reply	other threads:[~2024-11-30  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 15:13 bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets support Andrew De Angelis
2024-11-14  8:22 ` Eli Zaretskii
2024-11-30  9:46   ` Eli Zaretskii [this message]
2024-12-14  9:32     ` Eli Zaretskii

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=86bjxx9hqs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74295@debbugs.gnu.org \
    --cc=bobodeangelis@gmail.com \
    --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).