When I type "vim new.pl" (where new.pl does not exist) vim creates some basic perl lines for me depending on my ~/.vim/plugin/templates/perl-file-header. When this file exists everything is fine. If it does not exist vim "sometimes" issues a warning: "template file ~/.vim/plugin/templates/perl-file-header does not exist or is not readable." The first thing is this warning is not wrapped but simply truncated in case the terminal is not wide enough. If the terminal can display exactly the number of characters the warning consists of everything is fine. But if the terminal is wider (can display more characters), the warning is not shown at all. Reproducible: Always Steps to Reproduce: 1. Make sure you not have templates disabled in vim and that you did not create a ~/.vim/plugin/templates/perl-file-header file 2. Open a terminal, width 80 characters 3. vim new.pl -> issues warning, truncated instead of wrapped 4. rm new.pl 5. resize your terminal to e.g. 160 characters (such that the warning would fit completely) 6. vim new.pl -> no warning Expected Results: a) the warning should be wrapped when issued in a small terminal b) the warning should be there when issued in a large terminal I have app-editors/vim-7.0.174 with the following USE flags installed: -acl bash-completion -cscope gpm -minimal nls perl -python -ruby -vim-pager -vim-with-x I could reproduce this with a x11-terms/gnome-terminal-2.16.1 and x11-terms/xterm-222.
Sorry, but this is a bug with the source code of the package, so I'd suggest you send a message to bugs@vim.org. From the vim FAQ: 2.6. Where can I report bugs? First collect the required information using the following command: :source $VIMRUNTIME/bugreport.vim Now send the resulting text from the above command to the bugs@vim.org e-mail address. The Vim Development mailing list (see above) is a good place to discuss general bugs. If the bug you find is with syntax highlighting or some other "added feature" (i.e. not directly programmed into vim), attempt to inform the maintainer of that feature. For more information, read :help bug-reports
