Package: vim-runtime
Version: 2:9.1.0-1
Severity: normal
Hello!
I have recently noticed a regression.
Since one of the latest package upgrades (in Debian testing),
vim began to highlight some Fortran keywords, even when they appear
as part of identifiers. This is incorrect, since a keyword should
be highlighted only where it is actually a keyword, and not where
it appears as a part of an identifier.
Please see the attached 'test.f90' Fortran example program
and a screenshot of how vim highlights its syntax.
Please forward this bug report upstream and/or fix the regression,
as appropriate.
Thanks for your time.
P.S.: I believe that 'test.f90' is so trivial that it is not copyrighted.
Should it turn out to be copyrighted in some jurisdiction, I hereby release
it under the terms of the [Expat licence].
[Expat licence]: http://www.jclark.com/xml/copying.txt
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
vim-runtime depends on no packages.
Versions of packages vim-runtime recommends:
ii vim 2:9.1.0-1
ii vim-gtk3 [vim] 2:9.1.0-1
ii vim-tiny2:9.1.0-1
vim-runtime suggests no packages.
-- no debconf information
program test
integer :: mycalli
integer :: myifi
integer :: myendifi
integer :: mystopi
integer :: mycasei
integer :: myselecti
integer :: mywherei
integer :: myclassi
read(*,*) mycalli, myifi, myendifi, mystopi, mycasei, &
myselecti, mywherei, myclassi
write(*,*) mycalli + myifi + myendifi + mystopi + mycasei + &
myselecti + mywherei + myclassi
end
