Github posh git powershell inconsisitencies

Sgraffite

Senior member
Jul 4, 2001
209
149
116
I use posh git (installed with Github) under Windows powershell both at work and at home and powershell acts differently. I'm using Windows 7 Ultimate at home on my laptop, and Windows 8 at work.

At work when I run powershell using the purple icon Github puts on your desktop (labeled Git Shell) when you install it I get what I can best describe as a putty-esque interface. Putty-esque meaning I can click + drag then right click to copy, then right-click again to paste.

At home when I run powershell using the same desktop icon, I get the old command prompt style interface where to copy you have to right-click, then click mark, then click + drag to highlight and finally right click to copy. To pasteI have to right-click and choose paste from the context menu. This takes more than twice as long to perform the same action. If I hit the windows key and type powershell and hit enter I get the putty-esque powershell, but it seems completely oblivious to posh git as I lose all git functionality.

I'm guessing it's running the command prompt instead of powershell by default, but how do I change it? Both my home and work git shell shortcuts point to:
Code:
C:\Users\{Username}\AppData\Local\GitHub\GitHub.appref-ms --open-shell

Looking back I should have titled this "Github posh git powershell inconsisitencies"

Thread title changed by user request -- Programming Moderator Ken g6
 
Last edited by a moderator:

quikah

Diamond Member
Apr 7, 2003
4,227
769
126
Sounds like your work computer has quick edit mode enabled. Open properties for the icon. There should be an options tab where you can tick "quick edit mode".
 

Sgraffite

Senior member
Jul 4, 2001
209
149
116
Sounds like your work computer has quick edit mode enabled. Open properties for the icon. There should be an options tab where you can tick "quick edit mode".

That did the trick for at least the copy/paste part, thanks!

For setup, http://git-scm.com/book/en/v2/Git-in-Other-Environments-Git-in-Powershell

However, you could use registry hacks to open powershell instead of cmd.exe, but, I am unsure you want to go that route.

Ya, not sure I want to run into some weird future issue after I forgot I did that.