cvim.zip 6.1.1, what if the plugin is installed into another position then make a symbol link $HOME/.vim pointing to the installation folder? Should this be regarded as a user install?

[monkeyqyf]

For my case, I install the cvim plugin to another personal .vim.myself folder(my purpose is to share the vim configuration among virtual machines and remote hosts), then make a symbol link $HOME/.vim pointing to /xx/xx/.vim.myself.
For me, I expect this to be a user installation, and I could maintain all relevant files within my .vim.myself folder, while seems cvim will follow the symbol link to find the /xx/xx/.vim.myself then regards this as a system installation (because .vim.myself not in my home folder) and output "Please set your personal details in file /home/myname/.vim/c-support/templates/Templates".

[WolfgangMehner]

The detection (local/global installation) is done this way to deal with more complex system setups, which I guess you find in large institutions, where the home directories are distributed across several physical devices:
symbolic links:
/home/user_a/ -> /home2/user_a
/home/user_b/ -> /home3/user_b
actual data:
/home2/user_a/...
/home3/user_b/...
Until now, this was the most common bug report we got regarding this issue.

I would make the following suggestion, to fix the problem for now:
Create a directory
/xx/xx/.vim.myself/c-support/local-templates/
and put this line in your .vimrc:
let g:C_LocalTemplateFile = /xx/xx/.vim.myself/c-support/local-templates/Templates
then the automatically generated template file in ~/.vim/c-support/templates will not be used anymore and you can set your information in the centrally maintained file.

I will see whether there is a better automated solution. But we are hesitant to change the existing behavior, since from the user feedback thus far, this seems the best solution for most people.

[monkeyqyf]

Thanks for your response! While for the g:C_LocalTemplateFile solution, as I tried it doesn't work. Would you confirm if it's available in the latest version 6.1.1? Seems there isn't such variable but s:C_LocalTemplateFile as I greped.
Please correct me if I'm wrong. Maybe it's caused by my irregular configuration. Thanks.

[WolfgangMehner]

Was the directory ".../local-templates" (or whatever path you actually chose) created? Was the file inside it created?
Could you send me the output of?

:call C_Settings()

You can black out personal information.

The value of the global variable is copied into the local one by the call on line 233:

call :C_CheckGlobal('C_LocalTemplateFile ')

[monkeyqyf]

Hi,

Actually, my configuration is a little more complex than I presented above.
Let's show up the whole picture:

Regarding my ~/.vimrc, it's not a symbol link but an ordinary file. I append only one line:
source ~/.vimrc.yann

The ~/.vimrc.yann and ~/.vim.yann are symbol links pointing to /media/sf_env_share_folder/./home/.vimrc.yann and /media/sf_env_share_folder/./home/.vim.yann, which are in my virtualbox shared folder.

In my .vimrc.yann, I add following lines to load my .vim.yann.

if has('win32')
let &runtimepath.=','.escape(expand(':p:h'), ',').'.vim.yann'
elseif has('unix')
" Append the co-located .vim.yann into runtimepath,
let &runtimepath.=','.escape(expand(':p:h'), ',').'/.vim.yann'
let g:C_LocalTemplateFile =expand(':p:h').'/.vim.yann/c-support/templates/Templates'
" elseif has('mac')
" ......
endif

With above configuration, I could not impact too much of original .vimrc to load my center-maintained vim configuration and plugins. Maybe there's better way to implement.

The The output of :call C_Settings()
C/C++-Support settings

               author :  "YOUR NAME"
            authorref :  "y"
              company :  "NA"
     copyright holder :  "NA"
                email :  "NA"
              licence :  "NA"
         organization :  "IPPFRD"
              project :  ""
     C / C++ compiler :  gcc / g++
     C file extension :  "c"  (everything else is C++)
extension for objects :  ".o"

extension for executables : ""
compiler flags (C) : "-Wall -g -O0 -c"
linker flags (C) : "-Wall -g -O0"
libraries (C) : "-lm"
compiler flags (C++) : "-Wall -g -O0 -c"
linker flags (C++) : "-Wall -g -O0"
libraries (C++) : "-lm"
debugger : "gdb"
code snippet directory : "/media/sf_env_share_folder/home/.vim.yann/c-support/codesnippets/"
template style : "C"
plugin installation : "system"
global template file : "/media/sf_env_share_folder/home/.vim.yann/c-support/templates/Templates"
local template file : "/home/myname/.vim.yann/c-support/templates/Templates"
xterm defaults : -fa courier -fs 12 -geometry 80x24
dictionary file(s) :
current output dest. : vim
toolbox : Make (1.0.1)

---

C/C++-Support, Version 6.1.1 / Dr.-Ing. Fritz Mehner / mehner.fritz@fh-swf.de

[WolfgangMehner]

Well, the local template file seems to exist. Compare this line in the settings:

local template file : "/home/myname/.vim.yann/c-support/templates/Templates"

If you set your personal information there, the warning should disappear and your personal details should be inserted into the code in comments, ...

[monkeyqyf]

Yes, you are right.
let g:C_LocalTemplateFile = /xx/xx/.vim.myself/c-support/local-templates/Templates is helpful to me.
Thanks!