Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c++ files, and this worked well. However I decided to
On 9/10/06, Marius Roets [EMAIL PROTECTED] wrote:
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and
Marius Roets wrote:
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c++ files, and this worked well.
Hi Yakov,
On Sunday 10 September 2006 12:27, Yakov Lerner wrote:
I created file ~/bat/my.dir.vim/after/ftplugin/c/xxx.vim containing line
call input(This is after/ftplugin/c/xxx.vim)
and file ~/bat/my.dir.vim/after/ftplugin/cpp/cpp_xyz.vim containing line
call input(This is
Hi Tony,
On Sunday 10 September 2006 12:51, A.J.Mechelynck wrote:
AFAIK both sets should be loaded. See:
- BufRead and BufNewFile autocommands for the concerned file extension
(*.c, *.cpp, *.c++, etc.)
- FileType autocommand
- function s:LoadFTPlugin in $VIMRUNTIME/ftplugin.vim
- c
