Ben Fritz wrote:
> > > Previously, when I installed a plugin, I could set up mappings to that
> > > plugin's functionality by putting commands in
> > > ~/vimfiles/after/plugin/someplugin_maps.vim
> > >
> > > Now with packages, this no longer works, because loading plugins is done
> > > as wit
On Friday, August 5, 2016 at 2:08:15 PM UTC-5, Bram Moolenaar wrote:
> Ben Fritz wrote:
>
> > Previously, when I installed a plugin, I could set up mappings to that
> > plugin's functionality by putting commands in
> > ~/vimfiles/after/plugin/someplugin_maps.vim
> >
> > Now with packages, this
Ben Fritz wrote:
> Previously, when I installed a plugin, I could set up mappings to that
> plugin's functionality by putting commands in
> ~/vimfiles/after/plugin/someplugin_maps.vim
>
> Now with packages, this no longer works, because loading plugins is done as
> with ":runtime! plugin/**/*
Previously, when I installed a plugin, I could set up mappings to that plugin's
functionality by putting commands in ~/vimfiles/after/plugin/someplugin_maps.vim
Now with packages, this no longer works, because loading plugins is done as
with ":runtime! plugin/**/*.vim" BEFORE loading packages.