Commands after "endfunction | ..." were ignored

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
vim
Domain
tooling

Research direction

Start at autoload/vimlparser.vim around line 1434 and reproduce the issue with vimlparser#test() using the Vim script example. Trace how commands after endfunction | and endif | are parsed. Done means the output includes (echo 2345) and (echo 456) instead of dropping those commands.

Written by the indexing model from the issue text.

Description

endfunction の後の行の解析が捨てられているようです.

function! Hoo() abort
    echo 3
endfunction | echo 2345
if 1
  echo 4
endif | echo 456

なファイルを対象に vimlparser#test() すると、以下が出力され, (echo 2345) がありません

(function (Hoo)
 (echo 3))
(if 1
  (echo 4))
 (echo 456) 

以下の部分と思います
https://github.com/vim-jp/vim-vimlparser/blob/11d2beed1fd41f5d8b565a04f388261cdbd096a4/autoload/vimlparser.vim#L1434

Dominant language
Vim Script
Stars
173
Forks
28
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vim-jp/vim-vimlparser

All issues in vim-jp/vim-vimlparser

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.