* bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
@ 2018-01-14 15:27 Basil L. Contovounesios
2018-01-14 16:05 ` Eli Zaretskii
2019-11-17 8:16 ` Lars Ingebrigtsen
0 siblings, 2 replies; 5+ messages in thread
From: Basil L. Contovounesios @ 2018-01-14 15:27 UTC (permalink / raw)
To: 30112
Steps to reproduce:
1. emacs -Q
2. C-x h DEL
3. C-h e
4. M-: (setq bibtex-parse-keys-timeout 4) RET
[ or some other convenient value ]
5. M-x bibtex-mode RET
6. C-o
[ this (IMO) incorrectly inserts a large fill-prefix, but that's a
separate bug ]
After a few seconds of idle time, the following error is logged to
*Messages*:
Error during redisplay: (jit-lock-function 1) signaled
(args-out-of-range #<buffer *scratch*> 0 1)
After bibtex-parse-keys-timeout seconds of idle time, another error
appears:
Error running timer ‘bibtex-parse-buffers-stealthily’:
(wrong-type-argument number-or-marker-p nil)
Enabling debug on error does not provide much more context:
Debugger entered--Lisp error:
(wrong-type-argument number-or-marker-p nil)
bibtex-parse-keys(t)
bibtex-parse-buffers-stealthily()
apply(bibtex-parse-buffers-stealthily nil)
timer-event-handler
([t 0 4 0 t bibtex-parse-buffers-stealthily nil idle 0])
Note that step (6) is only needed to trigger the redisplay error; the
bibtex parse timer fails even when the buffer is empty.
--
Basil
In GNU Emacs 27.0.50 (build 15, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2018-01-11 built on thunk
Repository revision: e911587fb61bbc7f4be41e0a044cb6dee8f9e615
Windowing system distributor 'The X.Org Foundation', version 11.0.11905000
System Description: Debian GNU/Linux testing (buster)
Configured using:
'configure --config-cache --prefix=/home/blc/.local --with-mailutils
--with-x-toolkit=lucid --with-modules --with-file-notification=yes
--with-x 'CFLAGS=-flto -fomit-frame-pointer -march=native -maes -mavx
-mcrc32 -mf16c -mfpmath=sse -mfsgsbase -mfxsr -minline-all-stringops
-mmmx -mpclmul -mpopcnt -msahf -msse4.2 -mxsave -mxsaveopt -mvzeroupper
-O3 -pipe' LDFLAGS=-flto'
Configured features:
XAW3D XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS
NOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS LUCID X11 MODULES LIBSYSTEMD JSON LCMS2
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
2018-01-14 15:27 bug#30112: 27.0.50; bibtex-mode timer and redisplay errors Basil L. Contovounesios
@ 2018-01-14 16:05 ` Eli Zaretskii
2018-01-14 16:54 ` Basil L. Contovounesios
2019-11-17 8:16 ` Lars Ingebrigtsen
1 sibling, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2018-01-14 16:05 UTC (permalink / raw)
To: Basil L. Contovounesios; +Cc: 30112
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Sun, 14 Jan 2018 15:27:18 +0000
>
> Error during redisplay: (jit-lock-function 1) signaled
> (args-out-of-range #<buffer *scratch*> 0 1)
> [...]
>
> Note that step (6) is only needed to trigger the redisplay error
It's not a redisplay error, it's a JIT Font lock error. Redisplay
calls JIT lock as part of redisplaying the window, so it catches the
error and reports it.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
2018-01-14 16:05 ` Eli Zaretskii
@ 2018-01-14 16:54 ` Basil L. Contovounesios
2018-01-14 17:22 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Basil L. Contovounesios @ 2018-01-14 16:54 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 30112
Eli Zaretskii <eliz@gnu.org> writes:
> It's not a redisplay error, it's a JIT Font lock error. Redisplay
> calls JIT lock as part of redisplaying the window, so it catches the
> error and reports it.
Right, sorry - that was a thinko on my part.
Is it possible to reword debbugs subject lines?
--
Basil
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#30112: 27.0.50; bibtex-mode timer and redisplay errors
2018-01-14 15:27 bug#30112: 27.0.50; bibtex-mode timer and redisplay errors Basil L. Contovounesios
2018-01-14 16:05 ` Eli Zaretskii
@ 2019-11-17 8:16 ` Lars Ingebrigtsen
1 sibling, 0 replies; 5+ messages in thread
From: Lars Ingebrigtsen @ 2019-11-17 8:16 UTC (permalink / raw)
To: Basil L. Contovounesios; +Cc: 30112
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> Enabling debug on error does not provide much more context:
>
> Debugger entered--Lisp error:
> (wrong-type-argument number-or-marker-p nil)
> bibtex-parse-keys(t)
> bibtex-parse-buffers-stealthily()
> apply(bibtex-parse-buffers-stealthily nil)
> timer-event-handler
> ([t 0 4 0 t bibtex-parse-buffers-stealthily nil idle 0])
I've now added a sanity check to bibtex-parse-keys to abort in these
situations to Emacs 27.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-11-17 8:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-14 15:27 bug#30112: 27.0.50; bibtex-mode timer and redisplay errors Basil L. Contovounesios
2018-01-14 16:05 ` Eli Zaretskii
2018-01-14 16:54 ` Basil L. Contovounesios
2018-01-14 17:22 ` Eli Zaretskii
2019-11-17 8:16 ` Lars Ingebrigtsen
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.