unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 74750@debbugs.gnu.org, shipmints@gmail.com
Subject: bug#74750: clone-frame and make-frame pixelwise issues
Date: Tue, 17 Dec 2024 15:34:46 +0200	[thread overview]
Message-ID: <86h672o2kp.fsf@gnu.org> (raw)
In-Reply-To: <2d934c65-6cf5-4e6f-8dc4-5494433b27d0@gmx.at> (message from martin rudalics on Tue, 17 Dec 2024 10:02:13 +0100)

> Date: Tue, 17 Dec 2024 10:02:13 +0100
> Cc: 74750@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> 
>  > 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.
> 
> Shouldn't we have decided that at the time 'clone-frame' was proposed?
> Nowadays people might want to keep the selected frame alone; in
> particular if FRAME is not the selected frame.  It would make no
> difference here since 'make-frame' will automatically select the clone
> and give it input focus.

I see your point.  So let's leave that aspect alone.





  reply	other threads:[~2024-12-17 13:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 15:51 bug#74750: clone-frame and make-frame pixelwise issues Ship Mints
2024-12-10 12:27 ` Eli Zaretskii
2024-12-10 15:56   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-10 16:24     ` Ship Mints
2024-12-11  9:37       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 22:41         ` Ship Mints
2024-12-12  6:05           ` Eli Zaretskii
2024-12-12  9:22           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-13 10:30             ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-13 16:28               ` Ship Mints
2024-12-13 18:15                 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-13 18:25                   ` Ship Mints
2024-12-14  8:27                     ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-15 20:34                       ` Ship Mints
2024-12-16  9:23                         ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16  9:32                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 10:40                             ` Ship Mints
2024-12-16 10:48                               ` Ship Mints
2024-12-16 15:49                                 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 15:55                                   ` Ship Mints
2024-12-16 16:01                                     ` Ship Mints
2024-12-16 16:02                                       ` Ship Mints
2024-12-16 16:39                                   ` Ship Mints
2024-12-16 17:06                                     ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 17:32                                     ` Eli Zaretskii
2024-12-16 17:51                                       ` Ship Mints
2024-12-16 19:10                                         ` Eli Zaretskii
2024-12-17  1:20                                           ` Ship Mints
2024-12-17  9:02                                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-17 13:34                                             ` Eli Zaretskii [this message]
2024-12-16 19:13                                         ` Eli Zaretskii
2024-12-16 19:26                                           ` Ship Mints
2024-12-17  9:00                                       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-17 13:29                                         ` Eli Zaretskii
2024-12-18 10:05                                           ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 16:07                               ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 16:41                                 ` Ship Mints
2024-12-16 17:06                                   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-16 16:07                         ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86h672o2kp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74750@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=shipmints@gmail.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).