Downloads:

1,946

Downloads of v 1.0:

1,828

Last Update:

2/22/2015

Package Maintainer(s):

Software Author(s):

  • masoomshaikh

Tags:

edit path variable gui

Path Editor

1.0 | Updated: 2/22/2015

Downloads:

1,946

Downloads of v 1.0:

1,828

Maintainer(s):

Software Author(s):

  • masoomshaikh

Path Editor 1.0

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Failing Test


Validation Testing Unknown


Verification Testing Failed

Details

To install Path Editor, run the following command from the command line or from PowerShell:

>

To upgrade Path Editor, run the following command from the command line or from PowerShell:

>

To uninstall Path Editor, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade patheditor -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade patheditor -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure patheditor installed
  win_chocolatey:
    name: patheditor
    state: present
    version: 1.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'patheditor' do
  action    :install
  version  '1.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: patheditor,
    Version: 1.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller patheditor
{
   Name     = 'patheditor'
   Ensure   = 'Present'
   Version  = '1.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'patheditor':
  provider => 'chocolatey',
  ensure   => '1.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install patheditor version="1.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator purity on 3/5/2015.

Description

It provides a much easier way to view current entires in the path environment variable compared to the system's default editor as entries are displayed line by line.


tools\chocolateyInstall.ps1
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
if(!(Test-Path -Path $scriptPath)) {
	new-item -path $scriptPath -itemtype directory
}
$path = Join-Path $scriptPath PathEditor.exe
Write-Host "Installing to" $path
Get-ChocolateyWebFile 'PathEditor' $path 'https://patheditor2.codeplex.com/downloads/get/786268#'
tools\PathEditor.exe.gui
 

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

This package has no dependencies.

Discussion for the Path Editor Package

Ground Rules:

  • This discussion is only about Path Editor and the Path Editor package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Path Editor, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus