unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ship Mints <shipmints@gmail.com>
Cc: rudalics@gmx.at, 74750@debbugs.gnu.org
Subject: bug#74750: clone-frame and make-frame pixelwise issues
Date: Mon, 16 Dec 2024 19:32:22 +0200	[thread overview]
Message-ID: <86msgvpm8p.fsf@gnu.org> (raw)
In-Reply-To: <CAN+1HbqEO0nbA5ZdpUHS+Bmd088TUhjP7p6Tfdr_akYyFyVZ2A@mail.gmail.com> (message from Ship Mints on Mon, 16 Dec 2024 11:39:02 -0500)

> From: Ship Mints <shipmints@gmail.com>
> Date: Mon, 16 Dec 2024 11:39:02 -0500
> Cc: Eli Zaretskii <eliz@gnu.org>, 74750@debbugs.gnu.org
> 
> Patch attached.

Thanks.

>  (defun clone-frame (&optional frame no-windows)
>    "Make a new frame with the same parameters and windows as FRAME.
>  With a prefix arg NO-WINDOWS, don't clone the window configuration.
> +When the user option `frame-resize-pixelwise' is non-nil, and FRAME is

Please avoid using "when" as a conditional; use "if" instead.  "When"
can be interpreted as time-related condition, which is not what you
want.

> +not text-only, clone the originating frame's pixel size.  Otherwise, use
> +the number of FRAME's columns and lines for the clone.

This uses double negation, which makes the documentation harder to
understand.  Suggest to rephrase:

  By default, clone the pixel-size of the original frame, but if
  `frame-resize-pixelwise' is nil or FRAME is a text-only frame, use
  the FRAME's number of lines and columns for the clone.

> -    (unless (display-graphic-p)
> +    (unless (display-graphic-p frame)
>        (select-frame new-frame))

Why do you need this condition?





  parent reply	other threads:[~2024-12-16 17:32 UTC|newest]

Thread overview: 33+ 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 [this message]
2024-12-16 17:51                                       ` Ship Mints
2024-12-16 19:10                                         ` Eli Zaretskii
2024-12-16 19:13                                         ` Eli Zaretskii
2024-12-16 19:26                                           ` Ship Mints
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=86msgvpm8p.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).