-
### Problem
After accept a lsp snippet like `namespace` in c++, press `` jump to section `$0` in there is newline. and press `` again it jump to section `$1` instead insert a indent.
### Steps to r…
-
Currently, `silent` still prints the output to the command-line if `remote-expr` is used:
```
$ vim --servername vim123 --remote-expr "execute('silent echoerr 1')"
1
$ vim --servername vim123 …
-
### Steps to reproduce
Have these two test files
```bash
❯ head *
==> foobar test.vimrc
balki updated
29 minutes ago
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…
-
```
When using "NoMatchParen" (from the matchparen plugin in the runtime) via
a *ReadPre autocommand this might cause a E201, because it uses "windo"
and then the "(curbuf != old_curbuf)" check in Vi…