chrisbenti / ps-config

Powershell Config

ps-config

Screenshot

Installation

One Liner (run this in powershell as the current user context):

pushd "$env:USERPROFILE\Documents"; git clone --recursive https://github.com/chrisbenti/ps-config.git WindowsPowerShell; . $PROFILE; popd

You will also need ConEmu with one of the patched fonts

Testing

Testing is done with the Pester framework.

To execute tests, run "test.bat" from your profile root.

Inspiration and Resources

• Oh-My-ZSH Theme
• Patched Fonts

ps-config's Issues

Tab complete looks hideous...

The window that pops up when attempting to tab complete looks absolutely hideous. Is there a way to config this?

Better Readme to explain getting set up

Installation requires cloning to a directory that may already exist

Suggestion: change the installation directory so something unique. The installation commands listed in the README didn't work for me because I have already made some customizations to my powershell profile.

fatal: destination path 'WindowsPowerShell' already exists and is not an empty directory.
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git

Window type detection in Vanilla-Window function is terrible

See here

Create PowerShell module

Oh-My-Zsh creates a .zshrc that can override default configuration values, then calls the main script rather than including the entire prompt in the .zshrc. We should use a similar approach so we can do things like auto-update checks, config overrides, and better project organization.

I believe the way to do this is to create an actual PowerShell module that gets called by the Microsoft.PowerShell_profile.ps1 script when the shell is opened. This would also let us use PsGet for distribution and updates.

Subversion VCS root directory name shortened

Whereas hg and git root names are kept at full length. It's a quick fix, just wanted to make the issue.

Needs better name

We're treating this as similar to Oh-My-Zsh, but don't have a good name for it. If we want a cleaner update mechanism or better config overrides, we should really come up with a better name now, rather than try to rename things during install later.

Prompt shows ~ when in a deleted path

Repro:

1. Navigate to folder (where the folder is not ~)
2. Delete folder from another process
3. Press enter button (invoke prompt again)

Actual:

1. Prompt displays as "~"

Expected:
2. Prompt displays something more accurate

When in the root drive of powershell drives, the prompt is empty and gray

Make a new temporary drive similarly to this:

New-PSDrive -Name VM -PSProvider FileSystem -Root "\\win81-wwighamvm\c$"

Cd into it:

When in the root of the drive, the prompt is both empty and gray. (And when you cd into it, it becomes a UNC path, rather than a drive path) This probably isn't wholly intentional.

Would be great if this didn't "vendor" modules or submodule/subtree them

Could use something like Boxstarter or Chocolatey to handle the module versioning, this also prevents unexpected breakage when pulling in a version newer than what was last tested. Also would allow a "spec" file that shows what versions have been tested with Pester/Psake within the repo.

posh-hg/posh-svn prompt tags don't appear in ConEmu

The custom posh-git ones, ofc, do. Just wanted to note this for somewhere so I could fix it later.

New Pester Build Broke Tests

Looks like it's more stringent about some things, like when you Mock.