[vim/vim] Fortran syntax file broken (#5350)

52 views
Skip to first unread message

sambo57u

unread,
Dec 12, 2019, 9:11:11 AM12/12/19
to vim/vim, Subscribed

I am using vim under Fedora 31, current version 8.1.2424.

I am not sure exactly when but not so long ago everytime I edit a fortran file, I get the error messages
on the terminal from the fotrran.vim syntax file:

'Error detected while processing /usr/share/vim/vim81/syntax/fortran.vim:
line 188:
E869: (NFA) Unknown operator '@1'
E475: Invalid argument: fortranTarget^Idisplay^I"(<do\s+)@<11=\d+>"
line 277:
E869: (NFA) Unknown operator '@1'
E475: Invalid argument: fortranConstructName "(<end\sforall\s+)@<15=\a\w>"

The issue seems to be the < after @, e..g., @<15=... If I remove these < signs then
error goes away but I am not sure whether that is the right thing to do.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Christian Brabandt

unread,
Dec 12, 2019, 9:18:33 AM12/12/19
to vim/vim, Subscribed

Christian Brabandt

unread,
Dec 12, 2019, 9:19:13 AM12/12/19
to vim/vim, Subscribed

you could move the number before the <

Christian Brabandt

unread,
Dec 12, 2019, 9:19:40 AM12/12/19
to vim/vim, Subscribed

Please contact the maintainer of the file mentioned at the top.

sambo57u

unread,
Dec 12, 2019, 9:20:31 AM12/12/19
to vim/vim, Subscribed

Thanks, will do!

Ajit Thakkar

unread,
Dec 14, 2019, 10:46:42 AM12/14/19
to vim_dev
Sorry. My last update introduced this typo. 

An updated syntax file has been sent to Bram.

Ajit

Scott Lawrence

unread,
Jan 26, 2020, 1:53:36 AM1/26/20
to vim/vim, Subscribed

Checking [vim-dev], I see that the maintainer has sent a fix for the issue (off-list) to Bram. The fix doesn't appear to be in this repo yet. Is the fix available publicly, anywhere?

(@chrisbra's suggestion of just replacing <15= with 15<= and <11= with 11<= seems to work, but I really don't know. At least it gets rid of the error messages.)

Ajit Thakkar

unread,
Jan 26, 2020, 2:15:21 AM1/26/20
to vim_dev, reply+ACY5DGDO4AHMXIVSSU...@reply.github.com
I just resent the updated file to Bram. 

Cheers
Ajit

--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to a topic in the Google Groups "vim_dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_dev/mRTWthLMyvA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/5350/578473727%40github.com.

vim-dev ML

unread,
Jan 26, 2020, 2:15:46 AM1/26/20
to vim/vim, vim-dev ML, Your activity
I just resent the updated file to Bram.

Cheers
Ajit

On Sun, Jan 26, 2020 at 2:53 AM Scott Lawrence <vim-dev...@256bit.org>
wrote:

> Checking [vim-dev], I see that the maintainer has sent a fix for the issue
> (off-list) to Bram. The fix doesn't appear to be in this repo yet. Is the
> fix available publicly, anywhere?
>
> (@chrisbra <https://github.com/chrisbra>'s suggestion of just replacing

> <15= with 15<= and <11= with 11<= seems to work, but I really don't know.
> At least it gets rid of the error messages.)
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/vim/vim/issues/5350?email_source=notifications&email_token=ACY5DGELXPFQARVKNU4HKODQ7UXOVA5CNFSM4JZ7DQK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ5M57Y#issuecomment-578473727>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACY5DGGAHCPQUAKCPMBFKC3Q7UXOVANCNFSM4JZ7DQKQ>
> .

>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "vim_dev" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vim_dev/mRTWthLMyvA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vim_dev+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/5350/578473727%40github.com
> <https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/5350/578473727%40github.com?utm_medium=email&utm_source=footer>

Christian Brabandt

unread,
Jan 26, 2020, 8:52:00 AM1/26/20
to vim/vim, vim-dev ML, Comment

closing then.


You are receiving this because you commented.

Christian Brabandt

unread,
Jan 26, 2020, 8:52:01 AM1/26/20
to vim/vim, vim-dev ML, Comment

Closed #5350.


You are receiving this because you commented.

Scott Lawrence

unread,
Feb 3, 2020, 5:57:07 PM2/3/20
to vim/vim, vim-dev ML, Comment

I hate to be too much of a pest, but as this issue is not fixed in the repo, and the patch is not publicly available, I would suggest re-opening the issue and leaving it so for the time being.


You are receiving this because you commented.

K.Takata

unread,
Feb 3, 2020, 10:28:35 PM2/3/20
to vim/vim, vim-dev ML, Comment

I believe the change is already included in Bram's local repository and will be published in next runtime files update. Let's wait for it.


You are receiving this because you commented.

Bram Moolenaar

unread,
Feb 4, 2020, 4:33:41 PM2/4/20
to vim/vim, vim-dev ML, Comment

> I believe the change is already included in Bram's local repository and
> will be published in next runtime files update. Let's wait for it.

The version I have is from 2019 Dec 14. Not aware of a newer one.

--
This planet has -- or rather had -- a problem, which was this: most
of the people living on it were unhappy for pretty much of the time.
Many solutions were suggested for this problem, but most of these
were largely concerned with the movements of small green pieces of
paper, which is odd because on the whole it wasn't the small green
pieces of paper that were unhappy.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///


You are receiving this because you commented.

Ajit Thakkar

unread,
Feb 4, 2020, 4:45:28 PM2/4/20
to vim_dev
Bram wrote: 
The version I have is from 2019 Dec 14. Not aware of a newer one.

That 2019 Dec 14 version 102 is the latest one. But the faulty one in the repo is dated 2019 Nov 26 (version 101). 

Ajit

Bram Moolenaar

unread,
Feb 4, 2020, 5:08:55 PM2/4/20
to vim...@googlegroups.com, Ajit Thakkar
Did it somehow not get included in runtime updates? Strange.
Let me do it now.

--
What a wonderfully exciting cough! Do you mind if I join you?

Scott Lawrence

unread,
Feb 5, 2020, 2:52:50 AM2/5/20
to vim/vim, vim-dev ML, Comment

For clarity for anyone in the future: this issue is fixed by commit 560979ed....

Thanks all!


You are receiving this because you commented.

Reply all
Reply to author
Forward
0 new messages