Add user startup file for powershell

[Pireax]

The cmd version has a customizable file but powershell was missing one.

[jankatins]

vendor\init.bat got a comment at the top of the file not to change it. Maybe vendor/profile.ps1 should also get such a comment?

[Stanzilla]

@JanSchulz agree, done.

[pavelkouril]

Why not use the user profile though? Maybe @Jackbennett could say which option would be better?

[Stanzilla]

Related to #505 (comment) then. Depends on how you look at being portable, I guess.

[Pireax]

It isn't a question of if it's better to use a user profile or a portable profile file, with the portable profile file the option to use the user profile remains. This way we have both. The user can choose to run the user profile from the portable script or omit the -NoProfile launch option.

[Stanzilla]

Yup, my answer was more aimed at pavel, and the defaults we set.

[Pireax]

Mine too ;)

[Jackbennett]

I think using a cmder profile would be good. Anyone who wants to pull in their own PS Profile should know they can just dot source it . $profile.currentuserAllHosts

Although if you don't know powershell you won't have your own customized profile anyway.. hmm. Should cmder be it's own self contained little terminal or be a great baseline to add your own stuff onto that also happens to run portably.

Tough that it's not really I code problem. I vote use a cmder profile but keep in mind it's not a mandatory one. That's consistent with how cmd behaves and also doesn't have to worry about clobbering someone's main profile. At least until someone complains with a better/more informed use case.

[pavelkouril]

Yeah, true, you just can launch the $profile from this user startup file. Don't know why this didn't occur to me. :)