Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Linking dotfiles to another location
See original GitHub issueI understand that from the config usually you link to ~, and you can change this to another folder outside of home even.
I am setting up my dotfiles on a new drive (I’m replacing it), so while the new drive will be home later, right now it will be mounted somewhere else.
I am going to clone the dotfiles to that new drive, but if I run the script it will link to home.
How would I be able to link to the mounted drive? Would HOME=/mnt/home ./install be enough so the command thinks the mounted drive is the home?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Your shell expands $HOME based on its environment variables; if you do, e.g.
HOME=/mnt/new_home/brott $SHELLand then run those commands in the shell you just launched, it’ll work as you expect.After all, I ended up removing all the links manually. Then I started my computer with the new home drive, ran the script. Then rebooted so make sure everything was in order