From: JD Smith <jdtsmith@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68374@debbugs.gnu.org
Subject: bug#68374: min-width is not correctly treated by buffer-text-pixel-size
Date: Fri, 12 Jan 2024 11:45:02 -0500 [thread overview]
Message-ID: <F0D762CA-5C23-43DB-8032-4D16DCEDF93E@gmail.com> (raw)
In-Reply-To: <83ttnjjak5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
I suppose the occasional:
Error during redisplay: (jit-lock-function 3483) signaled (quit)
Error during redisplay: (jit-lock-function 3510) signaled (quit)
in *Messages* isn’t related or harmful? Soon I’ll be using pixel width calculations to layout the mode line; and will keep a close eye on it.
> On Jan 12, 2024, at 2:05 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: JD Smith <jdtsmith@gmail.com>
>> Date: Thu, 11 Jan 2024 14:53:57 -0500
>> Cc: 68374@debbugs.gnu.org
>>
>> Great, this small patch seems to work. I’ve enabled glyph checking and will report here if anything untoward comes up. Should I be keeping track of the *warnings* buffer?
>
> Yes, and also look out for redisplay errors in *Messages*.
>
> Thanks.
[-- Attachment #2: Type: text/html, Size: 1310 bytes --]
next prev parent reply other threads:[~2024-01-12 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 22:22 bug#68374: min-width is not correctly treated by buffer-text-pixel-size JD Smith
2024-01-11 10:24 ` Eli Zaretskii
2024-01-11 19:53 ` JD Smith
2024-01-12 7:05 ` Eli Zaretskii
2024-01-12 16:45 ` JD Smith [this message]
2024-01-12 18:09 ` Eli Zaretskii
2024-02-11 8:47 ` Eli Zaretskii
2024-02-11 12:20 ` JD Smith
2024-02-11 13:22 ` Eli Zaretskii
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=F0D762CA-5C23-43DB-8032-4D16DCEDF93E@gmail.com \
--to=jdtsmith@gmail.com \
--cc=68374@debbugs.gnu.org \
--cc=eliz@gnu.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).