mirror of
https://github.com/jorgebucaran/fisher
synced 2024-11-09 07:10:27 +00:00
888a9a0cf3
===================== Add user key bindings support. Recall $fisher_home/functions are always before user functions in $fish_function_path. This was an early design decision in order to prevent users from redefining core functions by mistake or by means other than using plugins (recommended). In other words, you are free to create a plugin that modifies a Fisherman core function, but you can't redefine a Fisherman function privately by saving it to your user config fish. If you found a bug in a Fisherman function, instead of creating a private patch send it upstream. If you created a function that overrides a Fisherman core feature, create a plugin. This way the community can benefit from your code whenever you are ready to publish it. By default, Fisherman provides no fish_user_key_bindings, so if the user has already defined their own fish_user_key_bindings that one will not be affected. Now, plugins can define their own key bindings inside a fish_user_key_bindings.fish or key_bindings.fish at the root of their repository or inside a functions directory. You can put your key bindings inside a function or not. If you put it inside a function, the function name must be the same as the file without the .fish extension. $fisher_config/bindings.fish When a plugin with key bindings is installed for the first time or the only one with bindings is uninstalled, Fisherman will modify ~/.config/functions/fish_user_key_bindings.fish (or create it for the first time) and add a single line at the top of the fish_user_key_bindings function to source the new $fisher_config/bindings.fish. All the key bindings defined by the enabled/installed plugins are concatenated and saved to this file. This mechanism has the following advantages: Does not slow down shell start. Does not require Fisherman to provide his own fish_user_key_bindings by default. Honors any previously existing user key bindings. Allows plugin to define their own key bindings and coexist with the user's key bindings. If the user updates his fish_user_key_bindings, re-running the function does update the key bindings. Mega Refactoring The entire source code of Fisherman received a major revision and refactoring. The validation and install/uninstall mechanisms were thoroughly revised and and broken down into smaller functions easier to test as well as several other sub parts of the system. Rewrite fisher search and remove features that are mostly already covered by fisher --list and remove the ability to generate information about plugins of unknown origin. The decision to remove this feature was based in performance concerns and the result of thinking about the usability and whether it was really worth the speed tradeoff. The conclusion is I would rather have better performance and if I need to query a plugins origin I can always use fisher --list or fisher --list=url or fisher --list=author. Add $fisher_update_interval to determine if the index should update or not when a search query is taking place. The default value is 10 seconds. This means the index will not be updated if less than 10 seconds have elapsed since the last action that triggered an update in the first place. See Improve Install/Uninstall/Update status output. If a plugin fails to install decrease the total. If any plugins are skipped because they are already installed in the case of fisher install or available in the cache, but disabled in the case of fisher uninstall they are collected into an array and displayed in a new section n plugin/s skipped (a, b, c) at the bottom of the report. Improve test coverage. Tightly coupled functions were making testing increasingly difficult. Most of the test effort was basically testing whether git clone or git pull. New separation of concerns makes tests run faster and the difficult install/uninstall algorithms has better coverage now. Other Now __fisher_list can list plugins from the cache, a fishfile/bundle and plugins that are installed/enabled or disabled. This removes __fisher_file and combines it with __fisher_list. This also removes fisher -f and replaces it with fisher -l <file> or fisher --list=<file>. Rename __fisher_parse_help to __fisher_complete and have the function create the completions automatically. This allows you to complete your commands with parseable usage help faster. The original design was fine, but this change improves auto-complete performance so it was preferred. Use __fisher_index_update when building file with Make. This helps prevent an error when using a fish version < 2.2.0. See #55 #50 #48. Add __fisher_index_update to update the index and remove previously undocumented fisher update --index. This function is designed to bypass GitHub's server network cache passing an arbitrary query string to curl like $fisher_index?RANDOM_NUMBER. This means index updates are immediately available now. Add fisher --list=url option to display local plugin url or path. Add fisher --list=bare option to display local plugins in the cache without the * enabled symbol. Prepend > to the currently enabled theme when using fisher --list[=cache]. Related #49. Prepend * to plugin names to indicate they are currently enabled when using fisher --list[=cache]. See #49.
353 lines
10 KiB
Groff
353 lines
10 KiB
Groff
.\" generated with Ronn/v0.7.3
|
|
.\" http://github.com/rtomayko/ronn/tree/0.7.3
|
|
.
|
|
.TH "FISHER\-TOUR" "7" "January 2016" "" "fisherman"
|
|
.
|
|
.SH "NAME"
|
|
\fBfisher\-tour\fR \- Fisherman Tour
|
|
.
|
|
.SH "DESCRIPTION"
|
|
Fisherman is a plugin manager and CLI toolkit for Fish to help you build powerful utilities and share your code easily\.
|
|
.
|
|
.P
|
|
Fisherman uses a flat tree structure that adds no cruft to your shell, making it as fast as no Fisherman\. The cache mechanism lets you query the index offline and enable or disable plugins as you wish\.
|
|
.
|
|
.P
|
|
Other features include dependency management, great plugin search capabilities and full compatibility with Tackle, Wahoo and oh\-my\-fish themes and packages\.
|
|
.
|
|
.P
|
|
This document describes Fisherman features and their implementation details\. For usage and command help see \fBfisher(1)\fR\.
|
|
.
|
|
.SH "FLAT TREE"
|
|
The configuration directory structure is optimized to help your shell start new sessions as quickly as possible, regardless of the numbers of plugins or prompts enabled at any given time\. An old saying goes that Fisherman is as fast as no Fisherman\.
|
|
.
|
|
.P
|
|
To explain how this is possible, we need to make a digression and discuss function scope first\. In fish, all functions share the same scope and you can use only one name per function\.
|
|
.
|
|
.P
|
|
In the following example:
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
function foo
|
|
echo $_
|
|
function bar
|
|
end
|
|
end
|
|
|
|
function bar
|
|
echo $_
|
|
end
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
\fIfoo\fR and \fIbar\fR are available immediately at the command line prompt and both print their names\. But there is a catch, calling \fIfoo\fR at least once will create a new \fIbar\fR function, effectively erasing the previous \fIbar\fR definition\. Subsequent calls to \fIbar\fR will print nothing\.
|
|
.
|
|
.P
|
|
By convention, functions that start with any number of underscores are \fIintentionally\fR private, but there is no mechanism that prevents you from calling them at any time once loaded\.
|
|
.
|
|
.P
|
|
With this in mind, it\'s possible to improve the slow shell start problem using a \fIflat\fR tree structure whose path is loaded only once\.
|
|
.
|
|
.P
|
|
The overhead of juggling multiple path hierarchies in a per\-plugin basis yields no benefits as everything is shared in the same scope\.
|
|
.
|
|
.P
|
|
Loading a path simply means adding the desired location to the \fB$fish_function_path\fR array\. See also \fBfunctions(1)\fR\.
|
|
.
|
|
.P
|
|
Here is a snapshot of a typical configuration path with a single plugin and prompt:
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
$fisher_config
|
|
|\-\- cache/
|
|
|\-\- conf\.d/
|
|
|\-\- |\-\- my_plugin\.config\.fish
|
|
|\-\- functions/
|
|
| |\-\- my_plugin\.fish
|
|
| |\-\- fish_prompt\.fish
|
|
| |\-\- fish_right_prompt\.fish
|
|
|\-\- completions/
|
|
| |\-\- my_plugin\.fish
|
|
|\-\- man/
|
|
|\-\- man1/
|
|
|\-\- my_plugin\.1
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
If you are already familiar in the way fish handles your user configuration, you will find the above structure similar to \fB$XDG_CONFIG_HOME/fish\fR\. See \fBInitialization Files\fR in \fBhelp fish\fR to learn more about fish configuration\.
|
|
.
|
|
.P
|
|
\fBconf\.d\fR, short for configuration directory, is used for initialization files, i\.e\., files that should run at the start of the shell\. Files that follow the naming convention \fB<name>\.config\.fish\fR are added there\.
|
|
.
|
|
.SS "PLUGINS"
|
|
Plugins are components that extend and add features to your shell\. To see what plugins are available use \fBfisher search\fR\. You can also type \fBfisher install\fR and hit \fItab\fR once to get formatted plugin information\. The same works for \fBfisher update\fR and \fBfisher uninstall\fR\.
|
|
.
|
|
.P
|
|
To learn how to create plugins, see \fBfisher help plugins\fR\.
|
|
.
|
|
.P
|
|
You can install a plugin by their name, URL or path to a local project\.
|
|
.
|
|
.P
|
|
If you use a \fIname\fR, this must be listed in the index database\. See \fBIndex\fR\.
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
fisher install shark
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
You can use an URL too if you have one\.
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
fisher install simnalamburt/shellder
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
If the domain or host is not provided, Fisherman will use \fBhttps://github\.com\fR by default\.
|
|
.
|
|
.P
|
|
In addition, all of the following \fBowner/repo\fR variations are accepted:
|
|
.
|
|
.IP "\(bu" 4
|
|
owner/repo \fB>\fR https://github\.com/owner/repo
|
|
.
|
|
.br
|
|
|
|
.
|
|
.IP "\(bu" 4
|
|
\fIgithub\fR/owner/repo \fB>\fR https://github\.com/owner/repo
|
|
.
|
|
.br
|
|
|
|
.
|
|
.IP "\(bu" 4
|
|
\fIgh\fR/owner/repo \fB>\fR https://github\.com/owner/repo
|
|
.
|
|
.br
|
|
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
Shortcuts to other common Git repository hosting services are also available:
|
|
.
|
|
.IP "\(bu" 4
|
|
\fIbb\fR/owner/repo \fB>\fR https://bitbucket\.org/owner/repo
|
|
.
|
|
.br
|
|
|
|
.
|
|
.IP "\(bu" 4
|
|
\fIgl\fR/owner/repo \fB>\fR https://gitlab\.com/owner/repo
|
|
.
|
|
.br
|
|
|
|
.
|
|
.IP "\(bu" 4
|
|
\fIomf\fR/owner/repo \fB>\fR https://github\.com/oh\-my\-fish/repo
|
|
.
|
|
.br
|
|
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
Because of Fisherman\'s flat tree model, there is no technical distinction between plugins or prompts\. Installing a prompt is equivalent to switching themes in other systems\. The interface is always \fIinstall\fR, \fIupdate\fR or \fIuninstall\fR\.
|
|
.
|
|
.P
|
|
Throughout this document and other Fisherman manuals you will find the term prompt when referring to the \fIconcept\fR of a theme, i\.e\., a plugin that defines a \fBfish_prompt\fR and / or \fBfish_right_prompt\fR functions\.
|
|
.
|
|
.SS "INDEX"
|
|
You can install, update and uninstall plugins by name, querying the Fisherman index, or by URL using several of the variations described in \fBPlugins\fR\. The index is a plain text flat database \fIindependent\fR from Fisherman\. You can use a custom index file by setting \fB$fisher_index\fR to your own file or URL\. Redirection urls are not supported due to security and performance concerns\. See \fBfisher help config\fR\.
|
|
.
|
|
.P
|
|
A copy of the index is downloaded each time a query happens\. This keeps the index up to date and allows you to search the database offline\.
|
|
.
|
|
.P
|
|
The index is a list of records, each consisting of the following fields:
|
|
.
|
|
.IP "\(bu" 4
|
|
\fBname\fR, \fBurl\fR, \fBinfo\fR, \fBauthor\fR and one or more \fBtags\fR\.
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
Fields are separated by a new line \fB\'\en\'\fR\. Tags are separated by one \fIspace\fR\. Here is a sample record:
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
shark
|
|
https://github\.com/bucaran/shark
|
|
Sparklines for your Fish
|
|
graph spark data
|
|
bucaran
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
To submit a new plugin for registration install the \fBsubmit\fR plugin:
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
fisher install submit
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
For usage see the bundled documentation \fBfisher help submit\fR\.
|
|
.
|
|
.P
|
|
You can also submit a new plugin manually and create a pull request\.
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
git clone https://github\.com/fisherman/fisher\-index
|
|
cd index
|
|
echo "$name\en$URL\en$info\en$author\en$tags\en\en" >> index
|
|
git push origin master
|
|
open http://github\.com
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
Now you can create a new pull request in the upstream repository\.
|
|
.
|
|
.SS "CACHE"
|
|
Downloaded plugins are tracked as Git repositories under \fB$fisher_cache\fR\. See \fBfisher help config\fR to find out about other Fisherman configuration variables\.
|
|
.
|
|
.P
|
|
When you install or uninstall a plugin, Fisherman downloads the repository to the cache and copies only the relevant files from the cache to the loaded function and / or completion path\. In addition, man pages are added to the corresponding man directory and if a Makefile is detected, the command \fBmake\fR is run\.
|
|
.
|
|
.P
|
|
The cache also provides a location for a local copy of the Index\.
|
|
.
|
|
.SS "FISHFILES"
|
|
Dependency manifest file, or fishfiles for short, let you share plugin configurations across multiple installations, allow plugins to declare dependencies, and prevent information loss in case of system failure\. See \fBfisher help fishfile\fR\.
|
|
.
|
|
.P
|
|
Here is an example fishfile inside \fB$fisher_config\fR:
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
# my plugins
|
|
gitio
|
|
fishtape
|
|
|
|
# my links
|
|
github/bucaran/shark
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
The fishfile updates as you install / uninstall plugins\. See also \fBfisher help install\fR or \fBfisher help uninstall\fR\.
|
|
.
|
|
.P
|
|
Plugins may list any number of dependencies to other plugins in a fishfile at the root of each project\. By default, when Fisherman installs a plugin, it will also fetch and install its dependencies\. If a dependency is already installed, it will not be updated as this could potentially break other plugins using an older version\. For the same reasons, uninstalling a plugin does not remove its dependencies\. See \fBfisher help update\fR\.
|
|
.
|
|
.SS "CONFIGURATION"
|
|
Fisherman allows a high level of configuration using \fB$fisher_*\fR variables\. You can customize the home and configuration directories, debug log file, cache location, index source URL, command aliases, etc\. See \fBfisher help config\fR\.
|
|
.
|
|
.P
|
|
You can also extend Fisherman by adding new commands and ship them as plugins as well\. Fisherman automatically adds completions to \fIcommands\fR based in the function \fIdescription\fR and usage help if provided\. See \fBfisher help help\fR and \fBfisher help commands\fR\.
|
|
.
|
|
.P
|
|
To add completions to standalone utility plugins, use \fBcomplete(1)\fR\.
|
|
.
|
|
.SS "CLI"
|
|
If you are already familiar with other UNIX tools, you\'ll find Fisherman commands behave intuitively\.
|
|
.
|
|
.P
|
|
Most commands read the standard input by default when no options are given and produce easy to parse output, making Fisherman commands ideal for plumbing and building upon each other\.
|
|
.
|
|
.P
|
|
Fisherman also ships with a CLI options parser and a background job wait spinner that you can use to implement your own commands CLI\. See \fBgetopts(1)\fR and \fBwait(1)\fR\.
|
|
.
|
|
.SH "COMPATIBILITY"
|
|
Fisherman supports oh\-my\-fish (Wahoo) themes and plugins by default, but some features are turned off due to performance considerations\.
|
|
.
|
|
.P
|
|
oh\-my\-fish evaluates every \fI\.fish\fR file inside the root directory of every plugin during initialization\. This is necessary in order to register any existing \fBinit\fR events and invoke them using fish \fBemit(1)\fR\.
|
|
.
|
|
.P
|
|
Since it is not possible to determine whether a file defines an initialization event without evaluating its contents first, oh\-my\-fish sources all \fB*\.fish\fR files and then emits events for each plugin\.
|
|
.
|
|
.P
|
|
Not all plugins opt in the initialization mechanism, therefore support for this behavior is turned off by default\. If you would like Fisherman to behave like oh\-my\-fish at the start of every session, install the \fBomf\fR compatibility plugin\.
|
|
.
|
|
.IP "" 4
|
|
.
|
|
.nf
|
|
|
|
fisher install omf
|
|
.
|
|
.fi
|
|
.
|
|
.IP "" 0
|
|
.
|
|
.P
|
|
This plugin also adds definitions for some of oh\-my\-fish Core Library functions\.
|
|
.
|
|
.SH "SEE ALSO"
|
|
fisher(1)
|
|
.
|
|
.br
|
|
fisher help
|
|
.
|
|
.br
|
|
fisher help config
|
|
.
|
|
.br
|
|
fisher help plugins
|
|
.
|
|
.br
|
|
fisher help commands
|
|
.
|
|
.br
|
|
wait(1)
|
|
.
|
|
.br
|
|
getopts(1)
|
|
.
|
|
.br
|
|
|