Bug with space in `syn region` regex
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- vim
- Domain
- devtools
Research direction
Reproduce the report with the foo.vim example and vint 0.3.21, then inspect how vim-vimlparser handles the syn region start regex containing an escaped space. The work is done when the valid command produces no parse error while the existing workaround remains unnecessary.
Written by the indexing model from the issue text.
Description
Example
❯ cat foo.vim
syn region foo start=/^ \+\|\tx/ end=/x/
Expected behavior
No parse errors, as this is valid.
Actual behavior:
❯ vint foo.vim
foo.vim:1:29: E10: \\ should be followed by /, ? or & (see vim-jp/vim-vimlparser)
Workaround
Wrap the space before the \t in [ ].
❯ cat foo.vim
syn region foo start=/^[ ]\+\|\tx/ end=/x/
❯ vint foo.vim
❯
Version information
❯ vint --version
0.3.21
❯ vim --version
NVIM v0.7.2
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by linuxbrew@649894113f22
❯ cat /etc/lsb-release
DISTRIB_ID=Pop
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Pop!_OS 20.04 LTS"
- Dominant language
- Vim Script
- Stars
- 173
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vim-jp/vim-vimlparser
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#201 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
vim-jp/vim-vimlparser#200 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#198 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#197 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
vim-jp/vim-vimlparser#174 ·
All issues in vim-jp/vim-vimlparser
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#13737 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4174 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
WingedGuardian/GENesis-AGI#2852 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
JuliusBrussee/caveman#1183 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#4432 ·
Maintainers usually reply within 1 day