unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ship Mints <shipmints@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>, 74750@debbugs.gnu.org
Subject: bug#74750: clone-frame and make-frame pixelwise issues
Date: Wed, 8 Jan 2025 12:50:53 -0500	[thread overview]
Message-ID: <CAN+1Hbon8Fft6Gb2J+nvKcNRn8bmwUZA4JqEVwN+dosRM295fw@mail.gmail.com> (raw)
In-Reply-To: <b26bdf64-77dc-4da2-955a-54350e0e8f47@gmx.at>

[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]

Hi, Martin,

Just got around to testing fullheight on GTK. Under emacs -Q, I do not see
a gap either on 29.4 or master from a week ago. This is on Debian 12 with
GTK 3.

-Stephane

On Mon, Dec 16, 2024 at 4:23 AM martin rudalics <rudalics@gmx.at> wrote:

>  > Now, about clone-frame. Are there any objections to the below
>  > implementation that uses text-pixels?
> ...
>  > When
>  > PIXELWISE is non-nil or if `frame-resize-pixelwise' is non-nil, and
> frame
>  > is not text-only, clone the originating frame's pixel size.
>
> I'd write that as
>
>    If PIXELWISE or `frame-resize-pixelwise' is non-nil and FRAME's terminal
>    is not text-only, use the pixel size of FRAME for the cloned frame.
>    Otherwise, use the number of columns and lines of FRAME for the cloned
>    frame.
>
> The behavior of the 'fullscreen' parameter might be queer if
> 'frame-resize-pixelwise' is nil and PIXELWISE is non-nil but that's to
> be expected.
>
>  > I may be able to test on GTK early this week, but I think you have GNU
>  > Linux/GTK on your end?
>
> I've tried here with a GTK-3 and a Motif build and have seen no
> problems.
>
> What I've seen is a slight misbehavior in setting up the 'fullscreen'
> parameter on the GTK build (so it's not related to your function).  With
>
> (setq frame-resize-pixelwise t)
> (setq frame-inhibit-implied-resize t)
>
> setting it to 'maximized' works as expected but setting it to
> 'fullheight' leaves a gap at the bottom.  Surprisingly, cloning a
> 'fullheight' frame with your function removes the gap.  The Motif frames
> do not have the problem so it might be tool bar related but that should
> affect the maximized frame as well.  I'll look into this later but would
> be interested if you see the same with a GTK build:
>
> To test:
>
> (setq frame-resize-pixelwise t)
> (setq frame-inhibit-implied-resize t)
> (set-frame-parameter nil 'fullscreen 'fullheight)
>
> martin
>

[-- Attachment #2: Type: text/html, Size: 2813 bytes --]

  parent reply	other threads:[~2025-01-08 17:50 UTC|newest]

Thread overview: 45+ 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
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
2025-01-08 17:50                           ` Ship Mints [this message]
2025-01-09  8:52                             ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 11:32                               ` Ship Mints
2024-12-16 16:07                         ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-20 15:39                         ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-22 12:04                           ` Ship Mints
2024-12-23 18:00                             ` 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=CAN+1Hbon8Fft6Gb2J+nvKcNRn8bmwUZA4JqEVwN+dosRM295fw@mail.gmail.com \
    --to=shipmints@gmail.com \
    --cc=74750@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rudalics@gmx.at \
    /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).