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

Chocolatey Installer - Don't use Write-Host #444

Closed
ferventcoder opened this issue Oct 2, 2015 · 0 comments
Closed

Chocolatey Installer - Don't use Write-Host #444

ferventcoder opened this issue Oct 2, 2015 · 0 comments

Comments

@ferventcoder
Copy link
Member

Prefer Write-Output instead. This will prevent issues for tools that may not have a host available in installing chocolatey itself.

@ferventcoder ferventcoder self-assigned this Oct 2, 2015
@ferventcoder ferventcoder added this to the 0.9.9.9 milestone Oct 2, 2015
ferventcoder added a commit to ferventcoder/choco that referenced this issue Oct 2, 2015
In installing chocolatey itself, the installer should use write-output
instead of write-host to prevent issues with tools that would install
Chocolatey but may not have a PowerShell console with a functioning
host.
ferventcoder added a commit that referenced this issue Oct 2, 2015
* stable:
  (GH-442) add conditional to prevent removal of unloaded modules
  (maint) Don't print chocolatey version every cmd
  (GH-444) Bootstrap - Write-Output over Write-Host

# Conflicts:
#	nuget/chocolatey/tools/chocolateysetup.psm1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants