emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#31440: closed (Can't redefine parent-frame on NS)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#31440: closed (Can't redefine parent-frame on NS)
Date: Sun, 03 Jun 2018 19:35:02 +0000

Your message dated Sun, 03 Jun 2018 20:34:22 +0100
with message-id <address@hidden>
and subject line Re: bug#31440: Can't redefine parent-frame on NS
has caused the debbugs.gnu.org bug report #31440,
regarding Can't redefine parent-frame on NS
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
31440: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31440
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Can't redefine parent-frame on NS Date: Sun, 13 May 2018 10:40:54 +0100 User-agent: Mutt/1.9.3 (2018-01-21)
from emacs -Q:

set up three frames, a, b and c:

    (set-frame-parameter c 'parent-frame a)

c becomes child of a.

(set-frame-parameter c 'parent-frame b)

expected: c becomes child of b and is no longer child of a.

actual: c remains child of a, and b now cannot be raised above a and b.

(set-frame-parameter c 'parent-frame nil)

expected: c ceases to be a child frame.

actual: emacs crashes.



Patch attached.

If this is too late for 26.1 I don’t think that will be a huge issue
as it seems redefining parent-frame is not something people want to
do, and it’s unlikely to be something a user does by accident.
-- 
Alan Third

Attachment: 0001-Fix-redefinition-of-child-frames-on-NS.patch
Description: Text document


--- End Message ---
--- Begin Message --- Subject: Re: bug#31440: Can't redefine parent-frame on NS Date: Sun, 03 Jun 2018 20:34:22 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (darwin)
Alan Third <address@hidden> writes:

> Patch attached.
>
> If this is too late for 26.1 I don’t think that will be a huge issue
> as it seems redefining parent-frame is not something people want to
> do, and it’s unlikely to be something a user does by accident.

Pushed to Emacs 26.2.
-- 
Alan Third


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]