Christian, thanks for your reply!
What would you say about such a scheme:
First, I have this defined in my .vimrc:
```VIMRC```
augroup MyAutoCmd
autocmd!
autocmd MyORIGINALFancyAutoCmdHere
augroup END
```VIMRC END```
Second, these triggers are present in the filetype-specific settings
Hi Folks,
I have been using dbext with my Postgres databases for quite some time and
really love it. Unfortunately, I have not been able to successfully connect
dbext to my MySQL databases. dbext + Postgres works just fine so I know (well,
assume) that the plugin and environment are working
On Tue, May 01, 2018 at 06:43:30PM +0200, Christian Brabandt wrote:
> On Mo, 30 Apr 2018, Danek Duvall wrote:
>
> > I've been trying to use v:termrbgresp to determine what color scheme to
> > use, but I can't figure out how to use it successfully.
> >
> > I tried simply testing against it in my
On Mo, 30 Apr 2018, Danek Duvall wrote:
> I've been trying to use v:termrbgresp to determine what color scheme to
> use, but I can't figure out how to use it successfully.
>
> I tried simply testing against it in my .vimrc, but that doesn't work,
> probably because it hasn't been set yet. Sort
On Di, 01 Mai 2018, ds wrote:
> Hi!
>
>
> Let's say I have an autocmd defined in my .vimrc, which applies to every
> possible buffer (autocmd-pattern is set to *). Now, is there any way to
> override this autocmd only for a particular filetype? I mean, to disable this
> "general" autocmd
Hi!
Let's say I have an autocmd defined in my .vimrc, which applies to every
possible buffer (autocmd-pattern is set to *). Now, is there any way to
override this autocmd only for a particular filetype? I mean, to disable this
"general" autocmd and to use another one instead? With the help of
While writing tests for my completion plugin (MUcomplete), I have
encountered some difficulty related to testing the auto-completion
functionality, which I try to reproduce below without my plugin, using
only core Vim commands.
I am not sure I have found the culprit yet, but I would appreciate
