Coder Social home page Coder Social logo

ps-config's Issues

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.

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

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.

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:
image

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.

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

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.