From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: eliz@gnu.org, 74496@debbugs.gnu.org
Subject: bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts
Date: Mon, 02 Dec 2024 15:47:35 +0000 [thread overview]
Message-ID: <dcs7c8inl2g.fsf@SDF.ORG> (raw)
In-Reply-To: <35e06858-90ec-48f1-9aca-557d0a8bb080@gmx.at> (message from martin rudalics on Sun, 1 Dec 2024 12:05:46 +0100)
martin rudalics <rudalics@gmx.at> writes:
> > The puzzle is why having only F11 `fullboth' fullscreens will shift the
> > bottom edge up by 8 pixels on CTWM restart.
>
> So I see two problems we have to investigate:
>
> - The fullscreen parameters are reset when restarting CWTM regardless of
> whether the frame was maximized or fullboth. This means that when you
> do F11, restart CWTM and do F11 again the frame will become fullscreen
> again. Right?
Yes.
> - The size of fullscreen frames shrinks by 8 pixels unless there is a
> maximized frame present.
That was the case when I was evaluating those expressions. But, now
fullboth and maximized frames will adjust up the bottom edge by 8
pixels.
> IIUC you are using Lucid. Now in xterm.c there are three instances of
>
> store_frame_param (f, Qfullscreen, lval);
>
> Can you put a breakpoint on each of them, ideally conditioned on lval
> equaling Qnil, restart CWTM and post a backtrace of whatever happens.
> I'd like to find out what kind of event makes us reset the parameter.
I pieced together the following steps to make emacs debuggable. I'll
need pointers to info pages to make progress.
a. make distclean
b. configure ... 'CFLAGS=-g3 -ggdb -Og ...'
c. make
i. start, emacs -Q
ii. use, M-x gdb
1 For help, type "help".
2 Type "apropos word" to search for commands related to "word"...
3 "0x7f7fff604da0s": not in executable format: file format not recognized
4 No symbol table is loaded. Use the "file" command.
5 Breakpoint 1 (xterm.c:18044) pending.
6 No symbol table is loaded. Use the "file" command.
7 Breakpoint 2 (xterm.c:28275) pending.
8 No symbol table is loaded. Use the "file" command.
9 Breakpoint 3 (xterm.c:28343) pending.
10 (gdb) run
11 The target does not support running in non-stop mode.
--
vl
next prev parent reply other threads:[~2024-12-02 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 18:28 bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 10:23 ` Eli Zaretskii
2024-11-30 10:36 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 13:03 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 16:53 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 18:21 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 19:01 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 19:25 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 8:46 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 9:59 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 11:05 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 14:26 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-01 17:50 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 16:04 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-03 8:24 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 15:47 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-02 16:22 ` Eli Zaretskii
2024-12-03 8:24 ` 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=dcs7c8inl2g.fsf@SDF.ORG \
--to=bug-gnu-emacs@gnu.org \
--cc=74496@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudalics@gmx.at \
--cc=van.ly@SDF.ORG \
/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).