GNU bug report logs - #74295
Update TODO -> NeXTstep port -> Improved xwidgets support

Previous Next

Package: emacs;

Reported by: Andrew De Angelis <bobodeangelis <at> gmail.com>

Date: Sun, 10 Nov 2024 15:14:01 UTC

Severity: normal

Tags: help

To reply to this bug, email your comments to 74295 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#74295; Package emacs. (Sun, 10 Nov 2024 15:14:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Andrew De Angelis <bobodeangelis <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 10 Nov 2024 15:14:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andrew De Angelis <bobodeangelis <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Update TODO -> NeXTstep port -> Improved xwidgets support
Date: Sun, 10 Nov 2024 10:13:17 -0500
[Message part 1 (text/plain, inline)]
Hello everyone.

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

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.


Thanks for all your work!
[Message part 2 (text/html, inline)]
[update-todo-for-xwidget-ns.patch (application/octet-stream, attachment)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#74295; Package emacs. (Thu, 14 Nov 2024 08:23:02 GMT) Full text and rfc822 format available.

Message #8 received at 74295 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrew De Angelis <bobodeangelis <at> gmail.com>,
 Po Lu <luangruo <at> yahoo.com>
Cc: 74295 <at> debbugs.gnu.org
Subject: Re: bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets
 support
Date: Thu, 14 Nov 2024 10:22:21 +0200
> From: Andrew De Angelis <bobodeangelis <at> 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.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#74295; Package emacs. (Sat, 30 Nov 2024 09:47:01 GMT) Full text and rfc822 format available.

Message #11 received at 74295 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: luangruo <at> yahoo.com
Cc: bobodeangelis <at> gmail.com, 74295 <at> debbugs.gnu.org
Subject: Re: bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets
 support
Date: Sat, 30 Nov 2024 11:46:19 +0200
Ping!

> Cc: 74295 <at> debbugs.gnu.org
> Date: Thu, 14 Nov 2024 10:22:21 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > From: Andrew De Angelis <bobodeangelis <at> 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.
> 
> 
> 
> 




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#74295; Package emacs. (Sat, 14 Dec 2024 09:33:02 GMT) Full text and rfc822 format available.

Message #14 received at 74295 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: luangruo <at> yahoo.com
Cc: bobodeangelis <at> gmail.com, 74295 <at> debbugs.gnu.org
Subject: Re: bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets
 support
Date: Sat, 14 Dec 2024 11:32:36 +0200
Ping! Ping!  Po Lu, can you please answer Andrew's question, if you
know the answer?

> Cc: bobodeangelis <at> gmail.com, 74295 <at> debbugs.gnu.org
> Date: Sat, 30 Nov 2024 11:46:19 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> Ping!
> 
> > Cc: 74295 <at> debbugs.gnu.org
> > Date: Thu, 14 Nov 2024 10:22:21 +0200
> > From: Eli Zaretskii <eliz <at> gnu.org>
> > 
> > > From: Andrew De Angelis <bobodeangelis <at> 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.
> > 
> > 
> > 
> > 
> 
> 
> 
> 




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#74295; Package emacs. (Sat, 28 Dec 2024 11:07:02 GMT) Full text and rfc822 format available.

Message #17 received at 74295 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: luangruo <at> yahoo.com
Cc: bobodeangelis <at> gmail.com, 74295 <at> debbugs.gnu.org
Subject: Re: bug#74295: Update TODO -> NeXTstep port -> Improved xwidgets
 support
Date: Sat, 28 Dec 2024 13:06:15 +0200
Ping! Ping! Ping! Po Lu, please respond.

> Cc: bobodeangelis <at> gmail.com, 74295 <at> debbugs.gnu.org
> Date: Sat, 14 Dec 2024 11:32:36 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> Ping! Ping!  Po Lu, can you please answer Andrew's question, if you
> know the answer?
> 
> > Cc: bobodeangelis <at> gmail.com, 74295 <at> debbugs.gnu.org
> > Date: Sat, 30 Nov 2024 11:46:19 +0200
> > From: Eli Zaretskii <eliz <at> gnu.org>
> > 
> > Ping!
> > 
> > > Cc: 74295 <at> debbugs.gnu.org
> > > Date: Thu, 14 Nov 2024 10:22:21 +0200
> > > From: Eli Zaretskii <eliz <at> gnu.org>
> > > 
> > > > From: Andrew De Angelis <bobodeangelis <at> 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.
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> 
> 
> 
> 




Added tag(s) help. Request was from Stefan Kangas <stefankangas <at> gmail.com> to control <at> debbugs.gnu.org. (Sat, 15 Feb 2025 03:28:02 GMT) Full text and rfc822 format available.

This bug report was last modified 125 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.