fix: parse arguments properly in certain circumstances

[amaanq]

Closes #102

Didn't test everything imaginable, but the ones linked in the issue parse fine now

vim.foo({bar})

vim.foo( {bar})

nvim_foo({bar})

nvim_foo({bar},{baz})

nvim_foo({bar}, {baz})

[clason]

Hmm, that fails two tests (tree-sitter test, or make all).

[amaanq]

that failing would make sense, i'll update the tests accordingly :) but idk why CI didn't catch that

[amaanq]

Seems like that might've fixed one of the tests anyways

[clason]

but idk why CI didn't catch that

because you didn't push the generated parser.c?

[clason]

I think you also need to add [ (see, e.g., :h nvim_buf_detach_event).

[clason]

And can you add a new test for these?

[amaanq]

done

[clason]

This adds a regression in indent.txt (:h ft-sh-indent) around

b:sh_indent_options['default']	Default amount of indent.

The 'default' is now recognized as a optionlink. (But not the lines below, curiously -- because they have a dash in them.)

There's also a few other regressions in taglinks, such as :h v_aB in motion.txt and |,| in map.txt (while most of them can be fixed by changing the help file, this cannot, so it's a blocker).

[amaanq]

Added another ugly hack for it, lmk of any others oddities

[clason]

Still breaks the taglink in map.txt.

[amaanq]

This flew off the radar...what's the taglink in map.txt? I'm unfamiliar with vimdoc semantics

[clason]

|,| (which is a link to the tag for ,).

[justinmk]

args may have whitespace ({arg arg}) but that's already tested on line 4

Actually, allowing whitespace in args is not part of vim's help syntax, and it causes lots of problems. So I reverted that "feature" in #97

[justinmk]

Looks worth a try. Thanks!

[justinmk]

Will revisit/rebase this after #97

[justinmk]

Rebased in #108

[justinmk]

Are [' and '] important special cases or could we drop these?

[clason]

I think that was done to work around the b:sh_indent_options mentioned earlier. So if those are fixed by your other changes (or deemed "won't fix" by simply wrapping them in backticks) they could indeed go.