Your message dated Sat, 21 Mar 2026 11:07:09 -0400
with message-id <ab6zk3IqXv-75Zq0@localhost>
and subject line Re: Bug#1127816: vim-nox: Python syntax highlighting exceeds
maxmempattern for long integers
has caused the Debian Bug report #1127816,
regarding vim-nox: Python syntax highlighting exceeds maxmempattern for long
integers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127816
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vim-nox
Version: 2:9.1.2103-1
Severity: normal
X-Debbugs-Cc: [email protected]
I observe a bug with the following setup:
docker run --rm -ti debian:testing
apt update
apt install vim-nox
echo
N=2140324650240744961264423072839333563008614715144755017797754920881418023447140136643345519095804679610992851872470914587687396261921557363047454770520805119056493106681
> a.py
vim --clean a.py
The outcome is that vim errors out with:
E363: Pattern uses more memory than 'maxmempattern'
As a consequence of that error, syntax highlighting is then no longer
active in the buffer.
The precise vim version is:
vim --version | head -n 2
VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Jan 23 2026 11:27:15)
Included patches: 1-948, 950-2103
Other versions checked:
More recent in Debian: The bug also occurs with 2:9.1.2141-1
Less recent in Debian: The bug does *not* occur with 2:9.1.1230-2
Upsteam has a strinkingly similar issue reported.
https://github.com/vim/vim/issues/19079
Apparently the collection of patches 1-2050 does not encounter the
issue, so the faulty patch might be in the set 949, 2051-2103
Best,
-- Package-specific info:
--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.nox
/usr/bin/vim is /usr/bin/vim.nox
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.17.11+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages vim-nox depends on:
ii libacl1 2.3.2-2+b2
ii libc6 2.42-11
ii libgpm2 1.20.7-12+b1
ii liblua5.1-0 5.1.5-11+b1
ii libperl5.40 5.40.1-7
ii libpython3.13 3.13.12-1
ii libruby3.3 3.3.8-2
ii libselinux1 3.9-4+b1
ii libsodium23 1.0.18-2
ii libtcl8.6 8.6.17+dfsg-1+b1
ii libtinfo6 6.6+20251231-1
ii vim-common 2:9.1.2103-1
ii vim-runtime 2:9.1.2103-1
vim-nox recommends no packages.
Versions of packages vim-nox suggests:
pn cscope <none>
pn vim-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:9.2.0218-1
On Fri, Feb 13, 2026 at 02:05:18PM +0000, Emmanuel Thomé wrote:
I observe a bug with the following setup:
docker run --rm -ti debian:testing
apt update
apt install vim-nox
echo
N=2140324650240744961264423072839333563008614715144755017797754920881418023447140136643345519095804679610992851872470914587687396261921557363047454770520805119056493106681
> a.py
vim --clean a.py
The outcome is that vim errors out with:
E363: Pattern uses more memory than 'maxmempattern'
This was fixed in the 2:9.2.0218-1 upload. I forgot to mention it in the
changelog for that upload.
Cheers,
--
James (he/him)
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
