Notices: This section not yet converted to new layout. Download stats are rolling back out.

Get-ChildItemColor (PowerShell Module)

2.1.1

Package test results are passing.

This package was approved by moderator gep13 on 7/30/2019.

Get-ChildItemColor provides colored version of Get-ChildItem Cmdlet and Get-ChildItem | Format-Wide (ls equivalent).

  • This adds colors to the output of Get-ChildItem Cmdlet of PowerShell. It is based on Tim Johnson’s script and another script by the PowerShell Guy.
  • Before version 1.0.0, the script actually had used Write-Host to write colored items on console. Now it just changes $Host.UI.RawUI.ForegroundColor and keep the item object intact. Hence, now one can use pipeline. (e.g., ~Get-ChildItemColor | grep “.git”~).
  • Get-ChildItemColorFormatWide still uses Write-Host for output however. This is because Get-ChildItemColor | Format-Wide does not allow multiple colors in one line. Hence, pipeline does not work with Get-ChildItemColorFormatWide.

NOTE: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.

To install Get-ChildItemColor (PowerShell Module), run the following command from the command line or from PowerShell:

C:\> choco install get-childitemcolor

To upgrade Get-ChildItemColor (PowerShell Module), run the following command from the command line or from PowerShell:

C:\> choco upgrade get-childitemcolor

Files

Hide
  • tools\.skipAutoUninstaller
  • tools\chocolateyBeforeModify.ps1 Show
    $ErrorActionPreference = 'Stop'
    
    $moduleName = $env:ChocolateyPackageName      # this could be different from package name
    Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue
  • tools\chocolateyInstall.ps1 Show
    $ErrorActionPreference = 'Stop'
    
    $toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
    $moduleName = $env:ChocolateyPackageName  # this may be different from the package name and different case
    $moduleVersion = $env:ChocolateyPackageVersion  # this may change so keep this here
    $savedParamsPath = Join-Path $toolsDir -ChildPath 'parameters.saved'
    
    # module may already be installed outside of Chocolatey
    Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue
    
    # remove the saved parameters file if it exists
    if (Test-Path -Path $savedParamsPath) {
        Remove-Item -Path $savedParamsPath -Force
    }
    
    $params = Get-PackageParameters
    
    $sourcePath = Join-Path -Path $toolsDir -ChildPath "$modulename.zip"
    $destinationPath = @()
    if ($params.Desktop -or (-not $params.Core)) {
        $desktopPath = Join-Path -Path $env:ProgramFiles -ChildPath "WindowsPowerShell\Modules\$moduleName"
    
        # PS > 5 needs to extract to a folder with the module version
        if ($PSVersionTable.PSVersion.Major -ge 5) {
            $desktopPath = Join-Path -Path $desktopPath -ChildPath $moduleVersion
        }
    
        $destinationPath += $desktopPath
    }
    
    if ($params.Core) {
        $destinationPath += Join-Path -Path $env:ProgramFiles -ChildPath "PowerShell\Modules\$moduleName\$moduleVersion"
    }
    
    ForEach ($destPath in $destinationPath) {
        Write-Verbose "Installing '$modulename' to '$destPath'."
    
        # check destination path exists and create if not
        if (Test-Path -Path $destPath) {
            $null = New-Item -Path $destPath -ItemType Directory -Force
        }
        Get-ChocolateyUnzip -FileFullPath $sourcePath -Destination $destPath -PackageName $moduleName
    
        # save the locations where the module was installed so we can uninstall it
        Add-Content -Path $savedParamsPath -Value $destPath
    }
    
    # For PowerShell 4 the module destination needs to be added to the PSModulePath
    if ($PSVersionTable.PSVersion.Major -lt 4) {
        $modulePaths = [Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';'
        if ($modulePaths -notcontains $destPath) {
            Write-Verbose "Adding '$destPath' to PSModulePath."
            $newModulePath = @($destPath, $modulePaths) -join ';'
    
            [Environment]::SetEnvironmentVariable('PSModulePath', $newModulePath, 'Machine')
            $env:PSModulePath = $newModulePath
        }
    }
    
    # cleanup the module from the Chocolatey $toolsDir folder
    Remove-Item -Path $sourcePath -Force -Recurse
  • tools\chocolateyUninstall.ps1 Show
    $ErrorActionPreference = 'Stop'
    
    $toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
    $moduleName = $env:ChocolateyPackageName  # this may be different from the package name and different case
    $savedParamsPath = Join-Path $toolsDir -ChildPath 'parameters.saved'
    
    if (Test-Path -Path $savedParamsPath) {
        $removePath = Get-Content -Path $savedParamsPath
    }
    else {
        $removePath = Join-Path -Path $env:ProgramFiles -ChildPath "WindowsPowerShell\Modules\$moduleName"
    }
    
    ForEach ($path in $removePath) {
        Write-Verbose "Removing all version of '$moduleName' from '$path'."
        Remove-Item -Path $path -Recurse -Force -ErrorAction SilentlyContinue
    }
    
    # remove path of module from $env:PSModulePath
    if ($PSVersionTable.PSVersion.Major -lt 4) {
        $modulePaths = [Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';'
    
        Write-Verbose "Removing '$sourcePath' from PSModulePath."
        $newModulePath = $modulePaths | Where-Object { $_ -ne $sourcePath }
    
        [Environment]::SetEnvironmentVariable('PSModulePath', $newModulePath, 'Machine')
        $env:PSModulePath = $newModulePath
    }
  • tools\Get-ChildItemColor.zip Show
    md5: 44BB74FA4FC0B74FA2347005081F60AE | sha1: BA3E595EEF6F52DF12D4BC1A7D683178DEC3A66D | sha256: 286F073CB677F7A215C3DC8E642DC62351C9FF5F93E4407F50A7C8D34019C4B1 | sha512: 3613D9547554A0E32760A48FFD358FB379B23363A38AC96C616D13339DDE18EDE26EF538198D3ADFD3575B741D703A1F375BA200EBD61169D622CA26CEC2F249
  • tools\LICENSE.txt Show
    From: https://github.com/joonro/Get-ChildItemColor/blob/master/LICENSE
    
    MIT License
    
    Copyright (c) 2018 Joon Ro
    
    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to deal
    in the Software without restriction, including without limitation the rights
    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
    copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:
    
    The above copyright notice and this permission notice shall be included in all
    copies or substantial portions of the Software.
    
    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    SOFTWARE.
  • tools\VERIFICATION.txt Show
    VERIFICATION
    Verification is intended to assist the Chocolatey moderators and community in verifying that this package's contents are trustworthy.
    
    To verify the files using the project source:
    
    1. Please go to the project source location (https://github.com/joonro/Get-ChildItemColor) and download the source files;
    2. Build the source to create the binary files to verify;
    3. Use Get-FileHash -Path <FILE TO VERIFY> to get the file hash value from both the built file (from step 1 above) and the file from the package and compare them;
    
    Alternatively you can download the module from the PowerShell Gallery ...
    
        Save-Module -Name Get-ChildItemColor -Path <PATH TO DOWNLOAD TO>
    
    ... and compare the files from the package against those in the installed module. Again use Get-FileHash -Path <FILE TO VERIFY> to retrieve those hash values.

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Joon Ro

Copyright

2018 Joon Ro

Tags

Release Notes

https://github.com/joonro/Get-ChildItemColor#changelog

Version History

Version Downloads Last updated Status
Get-ChildItemColor (PowerShell Module) 2.1.0 12 Monday, July 22, 2019 approved
Get-ChildItemColor (PowerShell Module) 2.0.0 14 Sunday, July 21, 2019 approved
Get-ChildItemColor (PowerShell Module) 1.2.3 273 Friday, May 18, 2018 approved

Discussion for the Get-ChildItemColor (PowerShell Module) Package

Ground rules:

  • This discussion is only about Get-ChildItemColor (PowerShell Module) and the Get-ChildItemColor (PowerShell Module) 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 Get-ChildItemColor (PowerShell Module), 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
Chocolatey.org uses cookies to enhance the user experience of the site.
Ok