-
Notifications
You must be signed in to change notification settings - Fork 82
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
Overhaul documentation #270
Conversation
PatrickF1
commented
Oct 20, 2022
•
edited
Loading
edited
- Refer to "search features" as "search commands", which is clearer.
- Clearly give each search command a capitalized, canonical name so it can be clearly referred to in the rest of the docs.
- Explicitly call out the "type" of the output of each command to be unambiguous.
- Add emojis in search command docs so they are more distinguishable when quickly scrolling.
- Make configuration docs more concise and clearer.
- Point out fd and bat only need to be installed if using Search Directory.
c027860
to
8fc977c
Compare
|
||
- add [key bindings](https://www.mankier.com/1/fzf#Key/Event_Bindings) within fzf to operate on the selected line: | ||
- [open file in Vim](https://github.com/junegunn/fzf/issues/1360) | ||
- [preview image files](https://gitter.im/junegunn/fzf?at=5947962ef6a78eab48620792) | ||
- [copy to clipboard](https://betterprogramming.pub/boost-your-command-line-productivity-with-fuzzy-finder-985aa162ba5d) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deleted this because it is now paywalled
|
||
### File paths |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding emojis to distinguish each section: currently, if you scroll quickly through the features, they all look about the same.
4014957
to
0e83f3c
Compare
The docs sometimes inconsistently referred to Search History as Search Command History, and Search Variables as Search Shell Variables. Use a consistent, canonical name so there is no ambiguity or confusion at all. That was one of the goals of #270.