You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vim configuration (including bundles in .vim) do not load. This is a generic Vim/Houdini integration problem, but it also prevents vex.vim from loading.
By default, Houdini modifies the HOME variable from c:\Users\USERNAME or c:\Users\USERNAME\Documents.
I've only experienced this issue on Windows 10. I'm not sure if it happens on macOS or Linux.
There are two workarounds, but unfortunately they must be done manually by the Vim user, since this bundle isn't loaded when the problem occurs.
Workaround 1
In houdini.env, change HOME back to c:\Users\YOUR_USERNAME.
On side effect of this is that some files that were written to c:\Users\USERNAME\Documents\houdini17.5 will now be written to c:\Users\USERNAME\houdini17.5.
Workaround 2
Place a .vimrc in c:\Users\USERNAME\Documents that sources c:\Users\USERNAME.
Workaround 3
Add an environment variable HOME to point to $env:USERPROFILE.
Possible Solution 1
Document problem in readme and in vim docs.
Print message describing problem the first time the bundle is loaded. Write a file (e.g., environment_problem_alert_shown) after this has occurred which is checked to prevent annoying messages each time the bundle is loaded.
The text was updated successfully, but these errors were encountered:
drichardson
changed the title
Bundle doesn't load with default Houdini HOME environment variable
Bundle doesn't load with default Houdini HOME environment value
Jun 1, 2019
Vim configuration (including bundles in .vim) do not load. This is a generic Vim/Houdini integration problem, but it also prevents vex.vim from loading.
By default, Houdini modifies the HOME variable from c:\Users\USERNAME or c:\Users\USERNAME\Documents.
I've only experienced this issue on Windows 10. I'm not sure if it happens on macOS or Linux.
There are two workarounds, but unfortunately they must be done manually by the Vim user, since this bundle isn't loaded when the problem occurs.
Workaround 1
In houdini.env, change HOME back to c:\Users\YOUR_USERNAME.
On side effect of this is that some files that were written to c:\Users\USERNAME\Documents\houdini17.5 will now be written to c:\Users\USERNAME\houdini17.5.
Workaround 2
Place a .vimrc in c:\Users\USERNAME\Documents that sources c:\Users\USERNAME.
Workaround 3
Add an environment variable HOME to point to $env:USERPROFILE.
Possible Solution 1
The text was updated successfully, but these errors were encountered: