I understand that chrome's API doesn't allow to read $HOME or ~/ in file path.
So you have to add your username in the configuration:
let configpath = '/home/myusername/.cvimrc'
This makes it an issue when saving your dotfiles on a public repository, as the config file becomes dependant on the user name. A temporary fix (until chrome allows access to $HOME?) would be maybe to add a new option with the file path, out of .cvimrc? This would also removes the need for "localconfig" (if a file is found it default to set localconfig).
I find it odd to add the file path or the local setting in the file itself and I was confused when setting cvim the first time.
I understand that chrome's API doesn't allow to read $HOME or ~/ in file path. So you have to add your username in the configuration:
let configpath = '/home/myusername/.cvimrc'
This makes it an issue when saving your dotfiles on a public repository, as the config file becomes dependant on the user name. A temporary fix (until chrome allows access to $HOME?) would be maybe to add a new option with the file path, out of .cvimrc? This would also removes the need for "localconfig" (if a file is found it default to
set localconfig
).I find it odd to add the file path or the local setting in the file itself and I was confused when setting cvim the first time.