Justin Rich

I guess that brings up a good point, should the docs be based on PS versions? i use to avoid the defined prefix because i had run in to problems...

@ekohl just out of curiosity, why? I've been talking to the folks in the irc channel and have been making some (painful) progress. At this point im using the centos7-devel,...

I guess i was thinking more of a Mouse over on the project, but the status bar is fine and i'll enable that. Yes, I'd basically like it to mirror...

Do you have an approach you'd like to take? I've poked at the code and i have a decent grasp of it but im not very good at TS so...

Just trying to think of how this would be used... here are some methods it could be used gci *.ps1 | add-gitchange # binds to inputobject [FileSystemInfo] has full name,...

i actually took that code already... i guess mostly what i was concerned about was passing 3 different types by pipe... filesysteminfo(binds to inputobject), strings (full path, partial path), change...

path spec wouldnt be positional.. so.. none of that would work..

so i think the -all is to just say add all changes, which, im not sure thats needed since you could just do **get-gitchange | add-gitchange** but, that was CMU's...

it should look for uncommitted changes before switching. allowing to -force if you accidently made changes on the wrong branch (additional file)

The text should be level, its just slightly off and it looks weird.. also, having the git orange in there would give it a little bit of life