wsllog.md

Base Windows 10

1. Installed NVM for Windows as my base WNT Node.js runtime
2. Installed Node.js 7.3.0 64-bit
3. Installed npm-windows-upgrade globally
4. Updated npm to 4.1.1

Microsoft Suggestions for Node.js: https://github.com/Microsoft/nodejs-guidelines

Things I've done to my WSL Subsystem

1. Blew away my entire existing WSL installation via lxrun /uninstall /full /y
2. Set Windows 10 to fast ring, waited 48 hours, and then updated to Build 14959.rs_prerelease
3. Rebuilt WSL via lxrun /unstall
4. Added symlink to my Windows Document dir
5. Added export PATH=$PATH:/mnt/c/"Program Files (x86)"/"Microsoft VS Code"/ to ~/.bashrc
6. Installed Jekyll and all associated Ruby dependencies
7. Installed testem
8. Installed postgresql using sudo apt-get install postgresql
9. Installed zsh and oh-my-zsh
10. Changed default WSL terminal to ZSH
11. Added export PATH=$PATH:/mnt/c/"Program Files (x86)"/"Microsoft VS Code"/ to ~/.zshrc
12. Created common ~/.aliases file with alias code='Code.exe . &'
13. Added the following to ~/.bashrc

if [ -f ~/.aliases ]; then
     . ~/.aliases
fi

14. Added the following to ~/.zshrc:

source $HOME/.aliases

15. Added export PATH=$PATH:/mnt/c/"Program Files (x86)"/Google/Chrome/Application/ to ~/.bashrc and ~/.zshrc
16. Added alias chrome='chrome.exe' to ~/.aliases
17. Installed nodemon globally using sudo apt-get install nodemon -g

Things I've done to my Console

1. Installed and configured Cmder in place of standard Windows 10 terminal
2. Configured ubuntu:: bash as Admin using the params *cmd /k "C:\Windows\System32\bash.exe" ~ -c zsh -cur_console:p to fix arrow issue and automatically launch zsh in place of bash.

Things I need to still do

1. Determine how I can automatically launch zsh as the Integrated Terminal in VSCode
2. Figure out how to use tabs and coloring properly in Cmder

Known Issues

1. When I run jekyll serve, jekyll only detects a single change. I need to run jekyll serve --force polling for this to work as expected
2. When I run vim using Cmder, I can't use my arrow keys when in INSERT. This ACTUALLY seems to be true for all of WSL under Cmder, as I can't arrow up to see previous commands when in BASH. --Fixed using -cur_console:p arg in Cmder
3. When I launch the VSCode windows binary, the process is blocking on the BASH terminal. My current workaround is to launch this as a background task, but this may be responsible for the .git lock file not getting properly cleaned up in my projects depending on the order in which I close my editor or shell.

References

• Using a common ~/.aliases file in both BASH and ZSH
• Searching the Issues of Microsoft's BashOnWindows repo is the best way to find fixes and workarounds
• Dave Rupert's #davegoeswindows blog posts