Downloads:
12,391
Downloads of v 0.7.7:
683
Last Update:
22 Jun 2017
Package Maintainer(s):
Software Author(s):
- Sam Hocevar
Tags:
wincompose compose composekey keyboard admin- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
WinCompose
This is not the latest version of WinCompose available.
- 1
- 2
- 3
0.7.7 | Updated: 22 Jun 2017
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
12,391
Downloads of v 0.7.7:
683
Maintainer(s):
Software Author(s):
- Sam Hocevar
WinCompose 0.7.7
This is not the latest version of WinCompose available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install WinCompose, run the following command from the command line or from PowerShell:
To upgrade WinCompose, run the following command from the command line or from PowerShell:
To uninstall WinCompose, run the following command from the command line or from PowerShell:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download wincompose --internalize --version=0.7.7 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade wincompose -y --source="'INTERNAL REPO URL'" --version="'0.7.7'" [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 wincompose -y --source="'INTERNAL REPO URL'" --version="'0.7.7'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install wincompose
win_chocolatey:
name: wincompose
version: '0.7.7'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'wincompose' do
action :install
source 'INTERNAL REPO URL'
version '0.7.7'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller wincompose
{
Name = "wincompose"
Version = "0.7.7"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'wincompose':
ensure => '0.7.7',
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.
This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.
- Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
- Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
- Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.
Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.
This package was approved by moderator AdmiringWorm on 24 Jun 2017.
A compose key allows to easily write special characters such as é ž à ō û ø ☺ ¤ ∅ « ♯ ⸘ Ⓚ ㊷ ♪ ♬ using short and often very intuitive key combinations. For instance, ö is obtained using o + ", and ♥ is obtained using < + 3. I wrote WinCompose because I found none of the alternatives (FreeCompose, CKFW, AllChars or Unichars) to be satisfying.
Log in or click on link to see number of positives.
- wincompose.0.7.7.nupkg (7f80b1f345f5) - ## / 59
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 |
---|---|---|---|---|
WinCompose 0.9.11 | 1699 | Friday, September 3, 2021 | Approved | |
WinCompose 0.9.10 | 598 | Friday, June 4, 2021 | Approved | |
WinCompose 0.9.8 | 356 | Tuesday, May 11, 2021 | Approved | |
WinCompose 0.9.7 | 233 | Friday, May 7, 2021 | Approved | |
WinCompose 0.9.6 | 617 | Friday, December 4, 2020 | Approved | |
WinCompose 0.9.5 | 214 | Sunday, November 29, 2020 | Approved | |
WinCompose 0.9.4 | 960 | Saturday, December 7, 2019 | Approved | |
WinCompose 0.9.3 | 344 | Sunday, November 17, 2019 | Approved | |
WinCompose 0.9.1-beta20190805 | 202 | Wednesday, August 7, 2019 | Exempted | |
WinCompose 0.9.1-beta20190405 | 200 | Tuesday, April 9, 2019 | Exempted | |
WinCompose 0.9.1-beta20190318 | 210 | Monday, March 18, 2019 | Exempted | |
WinCompose 0.9.0 | 618 | Sunday, March 17, 2019 | Approved | |
WinCompose 0.8.2 | 566 | Tuesday, August 21, 2018 | Approved | |
WinCompose 0.8.1 | 296 | Thursday, August 16, 2018 | Approved | |
WinCompose 0.8.0 | 518 | Friday, April 13, 2018 | Approved | |
WinCompose 0.7.7 | 683 | Thursday, June 22, 2017 | Approved | |
WinCompose 0.7.7-beta20170511 | 425 | Monday, May 15, 2017 | Exempted | |
WinCompose 0.7.6 | 625 | Tuesday, April 26, 2016 | Approved | |
WinCompose 0.7.4 | 532 | Tuesday, June 9, 2015 | Approved | |
WinCompose 0.7.2 | 504 | Saturday, April 4, 2015 | Approved | |
WinCompose 0.7.1 | 399 | Monday, March 16, 2015 | Approved | |
WinCompose 0.7.0 | 438 | Friday, March 13, 2015 | Approved | |
WinCompose 0.6.13 | 509 | Wednesday, December 17, 2014 | Approved | |
WinCompose 0.6.11 | 645 | Friday, August 22, 2014 | Approved |
Copyright (C) 2013-2017 Sam Hocevar
- This is a huge release.
-
- wincompose.install (= 0.7.7)
Ground Rules:
- This discussion is only about WinCompose and the WinCompose 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 WinCompose, 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.