Created attachment 286515 [details] c-support-5.15.1.ebuild app-vim/c-support-5.15.1 - version update
A message should be added after install, stating the user can create their own template by doing: ---------------------------------------------------------- mkdir -p $HOME/.vim/c-support/templates cp /usr/share/vim/vimfiles/c-support/templates/Templates \ $HOME/.vim/c-support/templates/ And edit: vi $HOME/.vim/c-support/templates/Templates to your liking ---------------------------------------------------------- However, I have a problem installing c-support system wide and then creating a custom Template within the $HOME/.vim/c-support folder as specified above as c-support does not seem to run as gracefully as when it is installed within the user's $HOME/.vim folder! Anybody else see this with bash-support or c-support vim plugins installed system wide vs. locally? (FYI: I've forwarded this issue to the authors mailing list.)
c-support-5.16 and fixes slow load times. I'm currently inquiring if this version also fixes system wide install issues. (bash-support and perl-support also have recent releases fixes slow load times as well. I'll try to package these soon after receiving confirmation system wide installs are fixed.)
Some further info on c-support-5.16, it now works installing system wide (and I believe this also includes bash-support as well). However, I'm inquiring the author about how a user is suppose to include the $HOME/.vim/c-support/templates/Template file. So far, users can include this file (using mkdir and cp the system installed "Templates" file) but they also need to comment out the include directives within the installed $HOME/.vim/c-support/templates/Template as they're already read in by the system wide Templates file. bash-support allows users to define these variables within their .vimrc file. I've made mention to the author this is probably the best method. (I'll await further info so I can provide einfo statements within the updated ebuild to instruct the user for defining these variables. Updating the bash-support & c-support ebuilds are as simple as changing the filename version number from c-support-5.15.ebuild to c-support-5.16.ebuild)
5.16.1 added to CVS. Open a new bug when/if you figure out some einfo statements.
