Re: How does one load plugin-specific settings after a plugin with the new packages feature?

2016-08-13 Thread Bram Moolenaar
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

Re: How does one load plugin-specific settings after a plugin with the new packages feature?

2016-08-12 Thread Ben Fritz
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

Re: How does one load plugin-specific settings after a plugin with the new packages feature?

2016-08-05 Thread Bram Moolenaar
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/**/*

How does one load plugin-specific settings after a plugin with the new packages feature?

2016-08-05 Thread Ben Fritz
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.