Couldn’t get this to work, but now it does, so… time for another “note to self”. 🙂
- Git, obviously…
- PuTTY, with puttygen, plink and pageant, to be exact…
- Open puttygen.
- Load your private key, or generate a new one and save it.
- Copy your public key (“Public key for pasting …”) to BitBucket/GitHub/etc.
- Open pageant
- Load your private key.
- Check that the key authentication works by running e.g.
plink -v email@example.com
plink -v firstname.lastname@example.org
- Point the GIT_SSH environment variable to plink.exe.
Now, as long as pageant is running with your private key loaded, it should work to clone, pull, push, etc. to/from both private and public repos. E.g.
git clone email@example.com:example/some-private-repo.git.
Key here, for me, was the GIT_SSH variable that so many blogs, StackOverflow answers and forum posts failed to mention… Without that set, the plink check did still work, but git clone did not. It just failed with an authentication error. With that variable set it now works perfectly. 🙄🙂👍
Sources: makandracards.com, vladmihalcea.com
Couldn’t find it… it’s somewhere… but at least, a quick way to get to it is:
On the Original:
%appdata%\Sublime Text 3\Packages\User to a synced folder.
- Make symbolic directory link from User to synced folder.
On the Other:
%appdata%\Sublime Text 3\Packages\User with symbolic directory link to the synced folder.
Tried moving my Documents/Desktop/Music/etc folders to a Google Drive mounted via Drive File Stream. Seemed to work well at first, but after the first reboot Windows clearly wasn’t happy and kept complaining about not finding the Desktop or the Documents…
Possibly because that drive seems to be mounted a bit too slowly (i.e. happens a bit after one has logged in)? And/or because it’s just mounted in a way Windows doesn’t like?
Either way, here’s how to…
- Open up regedit.
- Go to:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
- Update all incorrect values.
That seems to have fixed it for me anyways…
Apparently isn’t any
node.index property built-in, so here’s how to find it, in case I need it again:
let i = 0;
while(node = node.previousElementSibling) i++;