Load all opt plugins in a package at once?

(Sorry for yet another post, but I have embraced packages and I really like them!) To load all the optional plugins of a package a :packadd command must be issued once for each plugin. What do you think about adding a command that loads all the plugins in an opt directory at once? Something like

Re: Packages and plugin's subdirectories

On 2016-03-30 04:43:56 +, Nicola said: If that is the intended behaviour, maybe it should be noted more explicitly in the help files. In `:h packages`, it is written that Vim: Also note this difference: if pack/foo/opt/neocomplete is loaded during a session with `:packadd neocomplete`, onl

Re: Packages and plugin's subdirectories

On 2016-03-29 19:53:07 +, Bram Moolenaar said: Nicola wrote: Neocomplete's plugin folder is organized as follows: plugin/ neocomplete.vim neocomplete/ buffer.vim dictionary.vim tag.vim No matter whether neocomplete is in pack/*/start/ or in pack/*/opt/, only plugin/neocomplete.vim is loa

Re: Packages and plugin's subdirectories

2016-03-29 22:53 GMT+03:00 Bram Moolenaar : > > Nicola wrote: > >> Neocomplete's plugin folder is organized as follows: >> >> plugin/ >> neocomplete.vim >> neocomplete/ >> buffer.vim >> dictionary.vim >> tag.vim >> >> No matter whether neocomplete is in pack/*/start/ or in pack/*/op

Re: Packages and plugin's subdirectories

Nicola wrote: > Neocomplete's plugin folder is organized as follows: > > plugin/ > neocomplete.vim > neocomplete/ > buffer.vim > dictionary.vim > tag.vim > > No matter whether neocomplete is in pack/*/start/ or in pack/*/opt/, > only plugin/neocomplete.vim is loaded (at startup

Re: Does vimscript have a "stat()" command?

Josef Fortier wrote: >> I can suggest using filewritable() > Thanks! This works well > (FWIW I'm using filereadable() followed by filewriteable() to avoid no file > conditions). > Depending on what you're doing, you also might want to use isdirectory(). Regards, Chip Campbell -- -- You receive

Re: Does vimscript have a "stat()" command?

> I can suggest using filewritable() Thanks! This works well (FWIW I'm using filereadable() followed by filewriteable() to avoid no file conditions). -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more infor

Feature Request: i_CTRL-X_iCTRL-P draw from other buffers like i_CTRL-P

I've really come to enjoy the mapping (i've hijacked i_CTRL-J for it). It's more flexible then straight C-P, allowing a form of line completion. But it has one real drawback, it only draws from the current buffer. Is there a fundamental reason it can't draw completion candidates from other open

Packages and plugin's subdirectories

Neocomplete's plugin folder is organized as follows: plugin/ neocomplete.vim neocomplete/ buffer.vim dictionary.vim tag.vim No matter whether neocomplete is in pack/*/start/ or in pack/*/opt/, only plugin/neocomplete.vim is loaded (at startup or with :packadd, respectively). Is that a

Re: Build cexpr from result of python code.

On Thursday, March 24, 2016 at 9:22:37 PM UTC+1, ZyX wrote: > 2016-03-24 13:26 GMT+03:00 Ni Va : > > On Monday, March 21, 2016 at 4:45:45 PM UTC+1, ZyX wrote: > >> 2016-03-21 17:15 GMT+03:00 Ni Va : > >> > Hi, > >> > > >> > I am using Execute-selection-in-Python-and-append-master plugin in order >

Re: cmdheight

* Elimar Riesebieter [2016-03-26 16:24 +0100]: > Hi all, > > if I set cmdheight to a value greater than 1 I don't see the output > of ":echo b:variable" or "let b:variable" anymore. The result pops > up for a tenth of a sencind or so. It seems that a misconfigured vim-bufferline caused this pro