[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bundle doesn't load with default Houdini HOME environment value #6

Open
drichardson opened this issue Jun 1, 2019 · 0 comments
Open
Labels
bug Something isn't working

Comments

@drichardson
Copy link
Owner
drichardson commented 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

  1. Document problem in readme and in vim docs.
  2. 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.
@drichardson 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
@drichardson drichardson added the bug Something isn't working label Jun 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant