Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
fzf
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
fzf
Commits
d172c3ce
Commit
d172c3ce
authored
11 years ago
by
Junegunn Choi
Browse files
Options
Downloads
Patches
Plain Diff
Update README
parent
9904f535
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
README.md
+14
-6
14 additions, 6 deletions
README.md
with
14 additions
and
6 deletions
README.md
+
14
−
6
View file @
d172c3ce
...
...
@@ -313,12 +313,20 @@ export -f fzf
However, this is automatically set up in your .bashrc and .zshrc if you use the
bundled
[
install
](
https://github.com/junegunn/fzf/blob/master/install
)
script.
### Incorrect display on Ruby 1.8
It is reported that the output of fzf can become unreadable on some terminals
when it's running on Ruby 1.8. If you experience the problem, upgrade your Ruby
to 1.9 or above. Ruby 1.9 or above is also required for displaying Unicode
characters.
### Rendering issues
If you have any rendering issues, check the followings:
1.
Make sure
`$TERM`
is correctly set. fzf will use 256-color only if it
contains
`256`
(e.g.
`xterm-256color`
)
2.
If you're on screen or tmux, $TERM should be either
`screen`
or
`screen-256color`
3.
Some terminal emulators (e.g. mintty) have problem displaying default
background color and make some text unable to read. In that case, try
`--black`
option. And if it solves your problem, I recommend including it in
`FZF_DEFAULT_OPTS`
for further convenience.
4.
If you still have problem, try
`--no-256`
option or even
`--no-color`
.
5.
Ruby 1.9 or above is required for correctly displaying unicode characters.
### Ranking algorithm
...
...
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