Error: (NFA regexp) Can't have a multi follow a multi

[timfeirg]

environment:

 vi --version
NVIM v0.10.0-dev-5555+g3305bb9e4-Homebrew
Build type: Release
LuaJIT 2.1.1702233742

vimrc:

" vim-plug plugins {
call plug#begin('~/.nvim/plugged')
Plug 'ctrlpvim/ctrlp.vim'
" yankring inside ctrlp, as an extension
Plug 'tacahiroy/ctrlp-funky'
call plug#end()
" }


" ctrlp and plugins {
let g:ctrlp_mruf_case_sensitive = 0
let g:ctrlp_map = '<nop>'
let g:ctrlp_tilde_homedir = 1
let g:ctrlp_extensions = ['funky']
let g:ctrlp_custom_ignore = {
            \ 'dir':  'node_modules\|DS_Store\|vendor\|_book',
            \ 'file': '\v\.(log|so|pyc)$',
            \ }
" funky {
let g:ctrlp_funky_use_cache = 1
" after jump, move code to the center and open fold recursively
let g:ctrlp_funky_after_jump = 'zOzt'
let g:ctrlp_funky_nerdtree_include_files = 1
let g:ctrlp_funky_sort_by_mru = 1
let g:ctrlp_funky_syntax_highlight = 1
let g:ctrlp_funky_matchtype = 'path'
let g:ctrlp_follow_symlinks = 1
" t stands for tags
nnoremap t :CtrlPFunky<Cr>
nnoremap <leader>/ :CtrlPSearchHistory<CR>
" }
" }

to reproduce:

1. download pdpyras.py from https://github.com/PagerDuty/pdpyras/releases/tag/v4.5.0
2. unzip and edit pdpyras.py
3. trigger ctrlp-funky and navigate to send_event
4. try to use ctrlp-funky again and it will result in the following error:

Error detected while processing function ctrlp#funky#funky[18]..function ctrlp#funky#funky[13]..ctrlp#init[31]..<SNR>150_setlines_post[6]..ctrl
p#funky#init[20]..ctrlp#funky#candidates[12]..ctrlp#funky#extract:
line   16:
E871: (NFA regexp) Can't have a multi follow a multi
Press ENTER or type command to continue

[tacahiroy]

I don't reproduce the issue. Can you please give me information about your environment? Vim version, minimum .vimrc, etc. to reproduce.

Here is the environment in which I tried to reproduce the issue:

• Vim 9.1 (patch 1-366)
• ctrlp-funky b68fbb5

[timfeirg]

sorry, mine's neovim, don't know wether this problem should be posted here. but I've reduced my vimrc to produce a minimum config and updated the issue description.

if the problem is neovim's please close this issue and I'll search in neovim community