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

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

bug#57475: closed (29.0.50; Position problem with make-frame on Lucid bu


From: GNU bug Tracking System
Subject: bug#57475: closed (29.0.50; Position problem with make-frame on Lucid build)
Date: Thu, 01 Sep 2022 13:20:02 +0000

Your message dated Thu, 01 Sep 2022 21:18:42 +0800
with message-id <87ilm7mdvx.fsf@yahoo.com>
and subject line Re: bug#57475: 29.0.50; Position problem with make-frame on 
Lucid build
has caused the debbugs.gnu.org bug report #57475,
regarding 29.0.50; Position problem with make-frame on Lucid build
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57475: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57475
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 29.0.50; Position problem with make-frame on Lucid build Date: Mon, 29 Aug 2022 13:51:07 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)
On a Lucid build, make-frame appears to ignore the frame parameters
(left . 0) and (top . 0), when passed individually or together:

0. emacs -Q
1. M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (938 351)
2. M-: (make-frame)
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (938 350)
3. M-: (make-frame '((left . 0) (top . 0)))
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (938 350)
4. M-: (make-frame '((left . 0)))
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (938 350)
5. M-: (make-frame '((top . 0)))
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (938 350)

If one or both of the `top' and `left' parameters has a non-zero value,
that value is correctly realized; if only one of these parameters is
passed with a non-zero value, the other parameter is realized as 0:

5. M-: (make-frame '((left . 1) (top . 1)))
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (1 1)
6.  M-: (make-frame '((left . 1)))
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (1 0)
7. M-: (make-frame '((top . 1)))
   M-: (progn (list (alist-get 'left (frame-parameters))
                    (alist-get 'top (frame-parameters))))
=> (0 1)

The Gtk3 and non-toolkit builds do not have these problems, and on the
Lucid build, modify-frame-parameters and set-frame-position also work
fine with a 0 value of these parameters.


In GNU Emacs 29.0.50 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo
 version 1.17.6, Xaw scroll bars) of 2022-08-28 built on strobelfs2
Repository revision: 35af917f187719fecadde278a51fd10bf47eed07
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101004
System Description: Linux From Scratch r11.0-165

Configured using:
 'configure -C --with-x-toolkit=lucid --with-xinput2 'CFLAGS=-Og -g3''

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBSYSTEMD LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG RSVG
SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS WEBP X11 XDBE XIM
XINPUT2 XPM LUCID ZLIB



--- End Message ---
--- Begin Message --- Subject: Re: bug#57475: 29.0.50; Position problem with make-frame on Lucid build Date: Thu, 01 Sep 2022 21:18:42 +0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux)
Stephen Berman <stephen.berman@gmx.net> writes:

> On Wed, 31 Aug 2022 10:18:52 +0800 Po Lu <luangruo@yahoo.com> wrote:
>
>> Stephen Berman <stephen.berman@gmx.net> writes:
>>
>>> Sorry for the unclarity, I meant I clicked the frame that make-frame
>>> created.
>>
>> Should be fixed now, thanks.
>
> I confirm it is fixed - many thanks!
>
> Steve Berman

I'm closing this bug then, thanks.


--- End Message ---

reply via email to

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