Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

746,023

Downloads of v 1.3.24:

39,656

Last Update:

01 Oct 2023

Package Maintainer(s):

Software Author(s):

  • Samuel Vasko

Tags:

cmder console terminal cli foss

Cmder

  • 1
  • 2
  • 3

1.3.24 | Updated: 01 Oct 2023

Downloads:

746,023

Downloads of v 1.3.24:

39,656

Maintainer(s):

Software Author(s):

  • Samuel Vasko

Cmder 1.3.24

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

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

>

Deployment Method:

NOTE

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade cmder -y --source="'INTERNAL REPO 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 cmder -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install cmder
  win_chocolatey:
    name: cmder
    version: '1.3.24'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'cmder' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.3.24'
end

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


cChocoPackageInstaller cmder
{
    Name     = "cmder"
    Version  = "1.3.24"
    Source   = "INTERNAL REPO URL"
}

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


package { 'cmder':
  ensure   => '1.3.24',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved by moderator Pauby on 01 Oct 2023.

Description

Cmder is a software package created out of pure frustration over absence of usable console emulator on Windows. It is based on ConEmu with major config overhaul. Monokai color scheme, amazing clink and custom prompt layout.

The main advantage of Cmder is portability. It is designed to be totally self-contained with no external dependencies, that is makes it great for USB Sticks or Dropbox. So you can carry your console, aliases and binaries (like wget, curl and git) with you anywhere.

Combines utility of 3 distinct tools:

  • Console emulator = Conemu
  • Cmd.exe enhancements = clink
  • Unix tools on windows = msysgit

Notes

This package uncompresses to 250 MB and includes Unix commands via bundled msysgit.
See cmdermini (8 MB) for basic console without bundled msysgit.


legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://github.com/cmderdev/cmder/releases/tag/v1.3.24>
and can be verified by doing the following:

1. Download the following <https://github.com/cmderdev/cmder/releases/download/v1.3.24/cmder.7z>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum: 6786665A6CEA98520F5591D4BB7327477B53CFEA93FD22CA259363967BBF4BCD

The file 'LICENSE.txt' has been obtained from <https://github.com/cmderdev/cmder/blob/master/LICENSE>
legal\LICENSE.txt
MIT License

Copyright (c) 2017 Samuel Vasko

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\cmder.7z
md5: 62F3B4BE7FEFD7778BE391BF96521054 | sha1: B03F609567520E887E54E003500FEEA4EF4BD9AE | sha256: 6786665A6CEA98520F5591D4BB7327477B53CFEA93FD22CA259363967BBF4BCD | sha512: 6CFA1F94FD3486381DC73DC954BE4587F93A67FA7F8C670DB0DF29E88E642A568546E11E93B2BC832F897D12AEC2776938D5B6EAA3D836B83DE692921EF26F62
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  destination = Join-Path (Get-ToolsLocation) $env:ChocolateyPackageName
  file        = "$toolsPath\cmder.7z"
}

Get-ChocolateyUnzip @packageArgs
Remove-Item $toolsPath\*.7z -ea 0

Install-ChocolateyPath $packageArgs['destination'] 'User'
tools\Uninstall-ChocolateyPath.psm1
function Uninstall-ChocolateyPath {
  param(
    [string] $pathToUninstall,
    [System.EnvironmentVariableTarget] $pathType = [System.EnvironmentVariableTarget]::User
  )
  Write-Debug "Running 'Uninstall-ChocolateyPath' with pathToUninstall:`'$pathToUninstall`'";

  #get the PATH variable
  $envPath = $env:PATH
  #$envPath = [Environment]::GetEnvironmentVariable('Path', $pathType)
  if (!$envPath.ToLower().Contains($pathToUninstall.ToLower())) {
    Write-Host "PATH environment variable does not have $pathToUninstall in it."
    return
  }

  Write-Host "PATH environment variable has $pathToUninstall in it. Removing..."
  $actualPath = [Environment]::GetEnvironmentVariable('Path', $pathType)

  # escape regex metachars, match possible backslash and item separator at eol
  $pathToUninstallRegex = ($pathToUninstall -replace '([\\().])', '\$1') + '\\?(;|$)'

  # remove pathToUninstall from actualPath
  $actualPath = $actualPath -replace "$pathToUninstallRegex", ''

  if ($pathType -eq [System.EnvironmentVariableTarget]::Machine) {
    $psArgs = "[Environment]::SetEnvironmentVariable('Path',`'$actualPath`', `'$pathType`')"
    Start-ChocolateyProcessAsAdmin "$psArgs"
  }
  else {
    [Environment]::SetEnvironmentVariable('Path', $actualPath, $pathType)
  }

  # remove from path of current powershell session
  $envPSPath = $env:PATH
  $env:Path = $envPSPath -replace "$pathToUninstallRegex", ''
}
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$unScriptPath = Join-Path $toolsPath "Uninstall-ChocolateyPath.psm1"

$installPath = Join-Path (Get-ToolsLocation) $env:ChocolateyPackageName

Import-Module $unScriptPath
Uninstall-ChocolateyPath $installPath 'User'

if (Test-Path $installPath) {
  Remove-Item -path $installPath -Recurse -Force
}

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status
Cmder 1.3.21 31320 Thursday, May 4, 2023 Approved
Cmder 1.3.20 42667 Tuesday, October 18, 2022 Approved
Cmder 1.3.19 144187 Monday, January 17, 2022 Approved
Cmder 1.3.18 56922 Friday, March 26, 2021 Approved
Cmder 1.3.17 27316 Wednesday, December 23, 2020 Approved
Cmder 1.3.16 58205 Friday, July 31, 2020 Approved
Cmder 1.3.15 17857 Saturday, June 27, 2020 Approved
Cmder 1.3.14 50900 Thursday, January 9, 2020 Approved
Cmder 1.3.13 17395 Monday, November 25, 2019 Approved
Cmder 1.3.12 36786 Wednesday, August 21, 2019 Approved
Cmder 1.3.11 61637 Monday, December 24, 2018 Approved
Cmder 1.3.10 6837 Saturday, December 1, 2018 Approved
Cmder 1.3.9 345 Thursday, November 29, 2018 Approved
Cmder 1.3.8 6481 Tuesday, November 13, 2018 Approved
Cmder 1.3.7 1418 Saturday, November 10, 2018 Approved
Cmder 1.3.6 5172 Thursday, October 25, 2018 Approved
Cmder 1.3.5 46172 Sunday, February 11, 2018 Approved
Cmder 1.3.4 375 Thursday, March 29, 2018 Approved
Cmder 1.3.3 17850 Friday, November 3, 2017 Approved
Cmder 1.3.2 33872 Friday, December 16, 2016 Approved
Cmder 1.3.1.20161216 408 Friday, December 16, 2016 Approved
Cmder 1.3.1 4640 Wednesday, November 30, 2016 Approved
Cmder 1.3.0.20160620-beta 1003 Wednesday, June 22, 2016 Exempted
Cmder 1.3.0 10977 Wednesday, July 20, 2016 Approved
Cmder 1.3.0-beta 493 Saturday, May 21, 2016 Exempted
Cmder 1.2.9-beta 399 Saturday, May 21, 2016 Exempted
Cmder 1.1.4.102 532 Wednesday, June 22, 2016 Approved

Package changelog

Software changelog

IMPORTANT

🔴 This release updates a dependency with a known vulnerability, it is suggested that you update as soon as possible.

Please see additional notes section below for information about the upcoming changes in Cmder as well.

What's Changed

New Contributors

Additional Notes

Note 1: We're in the process of improving Cmder's initialization speed. In the next major release, the loading time is expected to be optimized significantly.

Note 2: Cmder is in the process of dropping 32-bit support of x86 edition when the upstream projects (such as Git-for-Windows) do so. In the next major releases of Cmder, the minimum Windows requirement will be bumped from Windows 7 SP1 to Windows 10, as well.

📌 Did you know Cmder also works with Windows Terminal? If you'd like to receive an official Cmder release with WT, please submit your vote here.

Full Changelog: https://github.com/cmderdev/cmder/compare/v1.3.21...v1.3.24


Discussion for the Cmder Package

Ground Rules:

  • This discussion is only about Cmder and the Cmder 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 Cmder, 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