From: Po Lu 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: Eli Zaretskii <eliz@gnu.org>,
Gregory Heytings <gregory@heytings.org>,
61704@debbugs.gnu.org
Subject: bug#61704: 29.0.60; Crash in get_narrowed_begv
Date: Thu, 23 Feb 2023 17:37:48 +0800 [thread overview]
Message-ID: <87bklkoh77.fsf@yahoo.com> (raw)
In-Reply-To: <f6e15cac-011c-038b-784b-3714068573a2@gmx.at> (martin rudalics's message of "Thu, 23 Feb 2023 10:33:42 +0100")
martin rudalics <rudalics@gmx.at> writes:
> So OT1H we really should set proper minimum size hints for the WM to
> avoid that resize_frame_windows has to deal with frame sizes it
> intrinsically cannot handle
Now this is not possible, as the window manager (or any X client, for
that matter) has free reign to do whatever it wants with another
client's window. Unless of course X server security policy prevents it.
> and OTOH the redisplay engine should be able to handle zero window
> sizes to avoid crashes the window code cannot prevent.
This is the only reasonable approach under X.
next prev parent reply other threads:[~2023-02-23 9:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874jrdq4ct.fsf.ref@po-lus-librem-15.mail-host-address-is-not-set>
2023-02-22 12:20 ` bug#61704: 29.0.60; Crash in get_narrowed_begv Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 12:48 ` Gregory Heytings
2023-02-22 12:59 ` Eli Zaretskii
2023-02-22 13:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 13:40 ` Gregory Heytings
2023-02-22 13:47 ` Eli Zaretskii
2023-02-22 14:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 14:18 ` Gregory Heytings
2023-02-22 13:17 ` Gregory Heytings
2023-02-22 13:44 ` Eli Zaretskii
2023-02-23 9:33 ` martin rudalics
2023-02-23 9:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-23 9:46 ` martin rudalics
2023-02-23 13:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 15:28 ` martin rudalics
2023-02-23 10:51 ` Eli Zaretskii
2023-02-23 13:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 10:54 ` Gregory Heytings
2023-02-23 13:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-23 13:23 ` Gregory Heytings
2023-02-23 15:28 ` martin rudalics
2023-02-23 15:54 ` Gregory Heytings
2023-02-23 17:41 ` martin rudalics
2023-02-23 10:44 ` Eli Zaretskii
2023-02-23 15:27 ` martin rudalics
2023-02-22 12:57 ` Eli Zaretskii
2023-02-22 13:23 ` Po Lu 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=87bklkoh77.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=61704@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=luangruo@yahoo.com \
--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 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.