Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
B
brew
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to JiHu GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
KMSCAKKSCFKA AKFACAMADCAS
brew
Commits
9a984681
Commit
9a984681
authored
13 years ago
by
Jack Nagel
Browse files
Options
Downloads
Patches
Plain Diff
doctor: correctly detect CLICOLOR_FORCE
Signed-off-by:
Jack Nagel
<
jacknagel@gmail.com
>
parent
0dbf06bb
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Library/Homebrew/cmd/doctor.rb
+3
-4
3 additions, 4 deletions
Library/Homebrew/cmd/doctor.rb
with
3 additions
and
4 deletions
Library/Homebrew/cmd/doctor.rb
+
3
−
4
View file @
9a984681
...
...
@@ -685,11 +685,10 @@ def check_for_MACOSX_DEPLOYMENT_TARGET
end
def
check_for_CLICOLOR_FORCE
target_var
=
ENV
[
'CLICOLOR_FORCE'
].
to_s
unless
target_var
.
empty?
if
ENV
[
'CLICOLOR_FORCE'
]
puts
<<-
EOS
.
undent
$CLICOLOR_FORCE
was set to
\"
#{
target_var
}
\"
.
Having $CLICOLOR_FORCE set can cause git builds to fail
.
Having
$CLICOLOR_FORCE
set can cause some builds to fail
.
You may want to unset it
.
EOS
end
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment