Miscellaneous Changes and Improvements

[thomasnorris]

• I found that the ~ symbol didn't seem to be working for my Cmder setup. I dug into the code and found that that symbol was being set when the user was in the HOME directory. My HOME directory is set to a location other than C:\users\myname, which would explain why the ~ appeared to not be working for me. I added a config setting that would allow the specification of a different environment variable other than HOME. For me, I have that set to USERPROFILE, but someone might want it to be HOMEDRIVE or another environment variable.
• Neither the optional git or npm symbols were working; the wrong variables were being used.
• I changed the way that the smart prompt type worked in git directories:
  • Before, just the folder would show. So if my git directory was C:\Users\me\cmder-powerline-prompt and I was inside the 'docs' folder, the folder would just show as docs. I figured that it would be better if it were to show cmder-powerline-prompt\docs to better give me an idea of where I was in the git directory.

I hope that these changes are useful! I know that they are (at least) to me, but I figured that maybe others would like them too.

[chrisant996]

re: the HOME part of the PR:

The intent for the HOME env var is that one sets it to one's home directory.
If the default value of HOME isn't right, then set it to the right value.

Doing that will make ~ in the prompt and ~ in Clink behave the same.

By using a different env var for ~ in the prompt, it makes the prompt show ~ in one directory, and Clink will expand/collapse ~ for a different directory. That seems confusing and might be more complicated than necessary.