From: Gregory Heytings <gregory@heytings.org>
To: martin rudalics <rudalics@gmx.at>
Cc: Po Lu <luangruo@yahoo.com>, Eli Zaretskii <eliz@gnu.org>,
61704@debbugs.gnu.org
Subject: bug#61704: 29.0.60; Crash in get_narrowed_begv
Date: Thu, 23 Feb 2023 15:54:39 +0000 [thread overview]
Message-ID: <96b742a05d89e5dd1aab@heytings.org> (raw)
In-Reply-To: <eafc4dc1-05a5-843d-53a1-2091e4e76714@gmx.at>
>> I maintain that the bug is (was) most probably not in get_narrowed_*. I
>> just built Emacs with the GTK, Lucid and no toolkits, I disabled
>> everything (tool-bar, menu-bar, scroll-bar, fringe-mode 0), and even
>> with that, after resizing the Emacs frame until it is literally a
>> single pixel on screen, I'm not able to get (under emacs -Q) a window
>> width or a height equal to 0 there. The smallest values I get are
>> width = 2 and height = 1.
>
> What you listed above is not likely to affect the height of a window -
> it's the header, mode and tab lines that count more.
>
Yes, I disabled all this to make sure the frame (and therefore the windows
on the frame) would become as small as possible. I tested this with emacs
-Q, with several windows on the frame displaying a buffer in which
(long-line-optimizations-p) is non-nil, without any header line or tab
line.
Perhaps I should have tried to disable the mode-line. Let's see...
M-: (setq mode-line-format nil) RET
No, still no way to get a zero height or width. Increasing or decreasing
the font size in the buffer also has no effect, I can't get a zero height
or width.
>
> Don't worry. What Po Lu saw is something I've seen in different forms
> much earlier. Small frames can be a problem for redisplay.
>
Indeed.
next prev parent reply other threads:[~2023-02-23 15:54 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
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 [this message]
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
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=96b742a05d89e5dd1aab@heytings.org \
--to=gregory@heytings.org \
--cc=61704@debbugs.gnu.org \
--cc=eliz@gnu.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 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).