Before Unison had LSP support for auto-completion, I added some hacky
auto-completion support to the vim plugin that called the codebase
server via curl and parsed the results with jq. The quality of the LSP
support now far exceeds this hacky completion, and I believe that the
hacky completion was accidentally disabled a while back anyway; so this
removes it.
Resolves#3847
Before this change if you had `{Abor<cursor>` and triggered completion,
nothing would be found because the `{` was included in the search
string. This change special-cases a few characters (braces, parentheses)
so that they don't accidentally get included in the search term.
I think that a fix that is 100% compatible with the Unison spec would be
more involved. But this seems to handle the vast majority of uses. Also
I don't think that the Unison parser even is 100% compatible with the
Unison spec 🙂.
Unison uses a comment like this to signal the fold after an `edit`
---- Anything below this line is ignored by Unison.
The previous definition of `uBelowFold` was a line starting with
"---- ". But in fact a fold is triggered by 3 or more dashes at the
start of a line, and doesn't require a space.
