GNU bug report logs - #74750
clone-frame and make-frame pixelwise issues

Previous Next

Full log

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

From: Ship Mints <shipmints <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rudalics <at> gmx.at, 74750 <at> debbugs.gnu.org
Subject: Re: bug#74750: clone-frame and make-frame pixelwise issues
Date: Mon, 16 Dec 2024 20:20:54 -0500

[Message part 1 (text/plain, inline)]

Maybe the compromise to unify the behavior is to always select the frame if
invoked interactively, otherwise not?

On Mon, Dec 16, 2024 at 2:10 PM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Ship Mints <shipmints <at> gmail.com>
> > Date: Mon, 16 Dec 2024 12:51:14 -0500
> > Cc: rudalics <at> gmx.at, 74750 <at> debbugs.gnu.org
> >
> > The tty test you're asking about was already in place, I merely added
> the missing frame argument that
> > ensures the test is against the source frame rather than the ambient
> selected-frame. As to its utility, I can go
> > only by the docstring sentence that reads "If the terminal is a
> text-only terminal then also select the new
> > frame." Seems to have originated with this commit
> 2c662e6d66165db8ead2f4d19a61af521807b8ba in 2021
> > when clone-frame was introduced.
>
> Martin, do we want to remove the condition?  I dislike such
> differences if they are not really necessary.  I understand why in the
> TTY case we must select the frame, but I don't understand why we
> refrain from doing so in the GUI case.
>
> WDYT?
>

[Message part 2 (text/html, inline)]

Previous Next

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