I am using vim under Fedora 31, current version 8.1.2424.
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.![]()
Yeah, this looks wrong:
As a workaround, try not to define the variable fortran_more_precise
you could move the number before the <
Please contact the maintainer of the file mentioned at the top.
Thanks, will do!
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.)
--
--
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.
closing then.
—
You are receiving this because you commented.
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.
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.
—
You are receiving this because you commented.
For clarity for anyone in the future: this issue is fixed by commit 560979ed....
Thanks all!
—
You are receiving this because you commented.