Cmder: powershell read user profile

[harkx]

Using 150513 it seems cmder does not use the Powershell profile.
I have a function in that profile to connect to Ofice365, it would be great if launching cmder reads the powershell proflile.

In my case it's located in:

C:\Users\me\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

You can query this location in Powershell with this command:

$Profile

[strig]

Go to settings > startup > tasks and remove the --NoProfile from the PowerShell command arguments.

[harkx]

Perfect! Thanks!

[nevion]

@strig why is this not default?

[Stanzilla]

I guess one could argue that to keep cmder properly portable it should ignore the local PS profile, not sure though

[jankatins]

Would it be a nice compromise to add someting like this into user_profile.ps:

# cmder runs the powershell with '--NoProfile', so $Profile isn't called on startup.
# If you want to use your $Profile, you can either uncomment the next lines or 
# change the startup to use $Profile (in cmder under settings > startup > tasks -> 
# remove the '--NoProfile' from the PowerShell command arguments).
#if (Test-Path $PROFILE) {
#    . $PROFILE
#} 

[Jackbennett]

What about a separate pre-configured task that doesn't have --noProfile. People can test with it and just move the default over if they choose.

[LexVocoder]

I was very puzzled why running PowerShell from the Start menu behaved differently from running it in Cmder. This cost me some time and effort to research the issue. Please fix. Thank you.

[daxgames]

@AlexHankins Add to the %cmder_root%\user_profile.ps1:

. $profile