From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Van Ly <van.ly@SDF.ORG>, Eli Zaretskii <eliz@gnu.org>
Cc: 74496@debbugs.gnu.org
Subject: bug#74496: 30.0.91; fullscreen frame set with F11 is shifted when ctwm restarts
Date: Wed, 4 Dec 2024 10:52:37 +0100 [thread overview]
Message-ID: <0c5b91ad-8f43-42ea-bbeb-5b9cdcb262a6@gmx.at> (raw)
In-Reply-To: <dcsa5dc58ra.fsf@SDF.ORG>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
> 33 (gdb) condition 1 lval == Qnil
> 34 No symbol "builtin_lisp_symbol" in current context.
I see. The condition would have been
condition 1 EQ (lval, Qnil)
but lval is not a C variable. So it won't work without modifying the
source. I have no good idea yet how to do that. Setting these
breakpoints unconditionally is out of the question - we want to catch
the transition from Qfullboth to Qnil here.
Maybe you can try the attached diff (it's against the release version)
and set breakpoints at the four lines I marked with a
// break-here
comment. Start gdb via run -Q, do F11 and restart CWTM. Here you have
to switch to the debugging Emacs (either you have it on another
workspace or you find an equivalent of Alt-TAB used by most window
managers) type "bt" and post the backtrace here. Maybe it will let us
find out why that parameter gets reset.
martin
[-- Attachment #2: break-fullscreen.diff --]
[-- Type: text/x-patch, Size: 2120 bytes --]
diff --git a/src/frame.c b/src/frame.c
index f6053fca3ef..e4787ae1bf5 100644
--- a/src/frame.c
+++ b/src/frame.c
@@ -4539,7 +4539,11 @@ gui_set_frame_parameters_1 (struct frame *f, Lisp_Object alist,
{
Lisp_Object old_value = get_frame_param (f, Qfullscreen);
- store_frame_param (f, Qfullscreen, fullscreen);
+ if (EQ (old_value, Qfullboth) && EQ (fullscreen, Qnil))
+ store_frame_param (f, Qfullscreen, fullscreen); // break here
+ else
+ store_frame_param (f, Qfullscreen, fullscreen);
+
if (!EQ (fullscreen, old_value))
gui_set_fullscreen (f, fullscreen, old_value);
}
diff --git a/src/xterm.c b/src/xterm.c
index fd3e58f85f6..3b5311b0977 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -18041,7 +18041,11 @@ x_net_wm_state (struct frame *f, Window window)
break;
}
- store_frame_param (f, Qfullscreen, lval);
+ if (EQ (get_frame_param (f, Qfullscreen), Qfullboth) && EQ (lval, Qnil))
+ store_frame_param (f, Qfullscreen, lval); // break here
+ else
+ store_frame_param (f, Qfullscreen, lval);
+
store_frame_param (f, Qsticky, sticky ? Qt : Qnil);
store_frame_param (f, Qshaded, shaded ? Qt : Qnil);
}
@@ -28272,7 +28276,11 @@ x_handle_net_wm_state (struct frame *f, const XPropertyEvent *event)
break;
}
- store_frame_param (f, Qfullscreen, lval);
+ if (EQ (get_frame_param (f, Qfullscreen), Qfullboth) && EQ (lval, Qnil))
+ store_frame_param (f, Qfullscreen, lval); // break here
+ else
+ store_frame_param (f, Qfullscreen, lval);
+
store_frame_param (f, Qsticky, sticky ? Qt : Qnil);
store_frame_param (f, Qshaded, shaded ? Qt : Qnil);
@@ -28340,7 +28348,10 @@ x_check_fullscreen (struct frame *f)
/* `x_net_wm_state' might have reset the fullscreen frame parameter,
restore it. */
- store_frame_param (f, Qfullscreen, lval);
+ if (EQ (get_frame_param (f, Qfullscreen), Qfullboth) && EQ (lval, Qnil))
+ store_frame_param (f, Qfullscreen, lval); // break here
+ else
+ store_frame_param (f, Qfullscreen, lval);
}
/* This function is called by x_set_offset to determine whether the window
next prev parent reply other threads:[~2024-12-04 9:52 UTC|newest]
Thread overview: 68+ 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-04 5:58 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04 9:53 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-05 2:39 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-05 9:23 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-05 11:14 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-05 18:02 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-06 10:42 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 14:03 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 15:52 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 16:33 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 17:36 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 6:26 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 16:57 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 18:01 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 9:10 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 14:48 ` Eli Zaretskii
2024-12-07 13:12 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 11:02 ` 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
2024-12-02 16:22 ` Eli Zaretskii
2024-12-04 5:15 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04 9:52 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-07 11:11 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 10:58 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 12:42 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 13:58 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 15:44 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-08 16:16 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 7:35 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 9:11 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 11:11 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-10 15:54 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-10 17:42 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 14:51 ` Eli Zaretskii
2024-12-09 17:14 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 18:13 ` Eli Zaretskii
2024-12-09 18:30 ` Eli Zaretskii
2024-12-11 17:00 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 9:22 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 13:40 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 17:18 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-13 9:38 ` Van Ly 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 11:28 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-14 9:20 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 13:42 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 14:57 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-20 6:37 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-20 9:24 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 22:42 ` 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-04 5:47 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-04 9:53 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0c5b91ad-8f43-42ea-bbeb-5b9cdcb262a6@gmx.at \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.