From: Eli Zaretskii <eliz@gnu.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: bug-gnu-emacs@gnu.org, notmuch@notmuchmail.org
Subject: Re: bug#59147: 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
Date: Wed, 09 Nov 2022 16:43:47 +0200 [thread overview]
Message-ID: <83r0yctcgs.fsf@gnu.org> (raw)
In-Reply-To: <87leokgpre.fsf@no.workgroup> (message from Gregor Zattler on Wed, 09 Nov 2022 15:35:01 +0100)
> From: Gregor Zattler <grfz@gmx.de>
> Cc: bug-gnu-emacs@gnu.org, notmuch@notmuchmail.org
> Date: Wed, 09 Nov 2022 15:35:01 +0100
>
> > The backtrace seems to indicate that it reads from the minibuffer, but
> > in that case, does it mean the mini-window was 7-lines high in this
> > case?
>
> quite possible, I have quite a few saved searches which are
> presented to me. The hight of the minibuffer also depends
> on the frames width. If the frame is half of the width of
> my monitor the choices are listed in 6 lines, then there is
> a blan line and a final line with a prompt. In fullscreen
> it's 3 lines of choices, the blank line and the prompt.
>
> > Also, can you describe what you do to trigger this assertion
> > violation?
>
> I can do so only on the level of user interaction: I call
> notmuch-jump-search via it's key binding which is key chord
> prefixed. Then I enter one or more chars to select the
> specific saved search I want to perform. It might be
> possible that I'm typing faster than Emacs performs this
> commands. Emacs hits the assertion with the choices still
> visible. I cannot say if it does so after my last key
> stroke or in the middel of them.
OK. I installed a possible fix. Can you update from Git, rebuild,
and see if it eliminates the assertions?
next prev parent reply other threads:[~2022-11-09 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 12:37 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows Gregor Zattler
2022-11-09 13:21 ` bug#59147: " Eli Zaretskii
2022-11-09 13:49 ` Gregor Zattler
2022-11-09 14:06 ` Eli Zaretskii
2022-11-09 14:35 ` Gregor Zattler
2022-11-09 14:43 ` Eli Zaretskii [this message]
2022-11-09 15:27 ` Gregor Zattler
2022-11-18 11:38 ` Gregor Zattler
2022-11-18 12:03 ` 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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r0yctcgs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=grfz@gmx.de \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).