From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 50096@debbugs.gnu.org
Subject: bug#50096: args-out-of-range in redisplay_internal
Date: Tue, 17 Aug 2021 20:18:16 +0300 [thread overview]
Message-ID: <83v94456sn.fsf@gnu.org> (raw)
In-Reply-To: <87r1esys1a.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 17 Aug 2021 19:06:41 +0300)
> From: Juri Linkov <juri@linkov.net>
> Date: Tue, 17 Aug 2021 19:06:41 +0300
>
> I prepared a commit message for the tab-bar patch, everything was nice,
> but suddenly the commit failed with an unexpected error:
>
> Debugger entered--Lisp error: (args-out-of-range 1737 1737)
> redisplay_internal\ \(C\ function\)()
> message("Running in foreground: %s" #("git --no-pager commit -m Redesign tab-bar event processing (bug#41342, bug#41343)\n\nInstead of emitting menu-item keys like [tab-1],\nemit normal mouse events like [mouse-1] and [mouse-2]\nfor
Is this reproducible? If so, put a breakpoint on args_out_of_range,
and show the C-level backtrace from the error.
next prev parent reply other threads:[~2021-08-17 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 16:06 bug#50096: args-out-of-range in redisplay_internal Juri Linkov
2021-08-17 17:18 ` Eli Zaretskii [this message]
2021-08-17 17:30 ` Juri Linkov
2021-08-17 17:51 ` Juri Linkov
2021-08-17 18:16 ` Eli Zaretskii
2021-08-17 18:24 ` Juri Linkov
2021-08-17 18:40 ` Eli Zaretskii
2021-08-17 18:51 ` Juri Linkov
2021-08-17 19:00 ` Eli Zaretskii
2021-08-18 7:42 ` Juri Linkov
2021-08-18 12:18 ` Eli Zaretskii
2021-08-18 16:32 ` Juri Linkov
2021-08-18 17:01 ` Eli Zaretskii
2021-08-18 18:07 ` Eli Zaretskii
2021-08-19 7:17 ` Juri Linkov
2021-08-19 8:12 ` Eli Zaretskii
2021-08-19 12:39 ` Eli Zaretskii
2021-08-20 7:09 ` Juri Linkov
2021-08-20 7:49 ` Eli Zaretskii
2021-08-19 7:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v94456sn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50096@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.