Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helper function using powershell to register the cmder context menu #441

Merged
merged 1 commit into from
Mar 25, 2015

Conversation

Jackbennett
Copy link
Contributor

I wanted to start work on just having a cmder powershell module for us to use to build the packages and also expose any settings we like through it. adding features to the scripts/ bit to just town the whole folder into a module and move it to vendor/

A neat by product is that users can now re-run this command and set custom
icons.

Some problems;

  • This function must be run as an administrator since we're touching the registry.
  • I'm not sure what the %V command does but it's not opening in the targeted
    folder as yet.
  • The output is a little ugly at present.

Apparently my pull requests come in pairs.

Function must be run as an administrator since we're touching the
registry.

A neat by product is that users can now re-run this command and set custom
icons.

I'm not sure what the `%V` command does but it's not opening in the targeted
folder as yet.

The output is a little ugly at rpesent.
MartiUK added a commit that referenced this pull request Mar 25, 2015
Helper function using powershell to register the cmder context menu
@MartiUK MartiUK merged commit 4f0e51c into cmderdev:development Mar 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants