| doc | ||
| test | ||
| zmodules | ||
| _zplugin | ||
| LICENSE | ||
| README.md | ||
| zplugin-autoload.zsh | ||
| zplugin-install.zsh | ||
| zplugin.zsh | ||
Zplugin
Zplugin gives reports from plugin load. Plugins are no longer black boxes,
report will tell what aliases, functions, bindkeys, Zle widgets, zstyles,
completions, variables, PATH and FPATH elements a plugin has set up. Supported is
unloading of plugin and ability to list, uninstall, reinstall and selectively
disable, enable plugin's completions. Also, every plugin is compiled and user
can control this function. The system does not use $FPATH, it's kept clean!
Code is immune to KSH_ARRAYS, emulate sh, emulate ksh, thoroughly tested to
support any user setup, be as transparent as plain source command. Completion
management functionality is provided to allow user call compinit only once in
.zshrc.
Quick start
To install, execute:
sh -c "$(curl -fsSL https://raw.githubusercontent.com/psprint/zplugin/master/doc/install.sh)"
Then add to ~/.zshrc, at bottom:
zplugin load psprint zsh-navigation-tools
zplugin load psprint---zprompts
zplugin load zsh-users/zsh-autosuggestions
zplugin light zsh-users/zsh-syntax-highlighting
(No need to add:
source "$HOME/.zplugin/bin/zplugin.zsh"
because the install script does this.)
ZNT – multi-word searching of history (Ctrl-R), zprompts – a few themes
with advanced Git features (add promptinit; prompt scala4 to ~/.zshrc to
set a prompt).
News
-
14-05-2017
- The
all-variants of commands (e.g.update-all) have been merged into normal variants (with--allswitch)
- The
-
13-05-2017
-
Bug fixes related to local plugins
-
100msgain in performance -
When updating plugin a list of new commits is shown
-
lftpas fallback transport support for snippets -
Snippets support
ftpandscpprotocols -
With snippets you can load a file as command that is added to PATH:
% zplg snippet --command https://github.com/b4b4r07/httpstat/blob/master/httpstat.sh % httpstat.sh too few arguments -
Snippets are updated on
update --allcommand
-
Screencasts
Dtrace:
Code recognition with recently, changes, glance, report, stress:
Introduction
Example use:
% . ~/github/zplugin/zplugin.zsh
% zplugin light zsh-users/zsh-syntax-highlighting
% zplugin load psprint/zsh-cmd-architect
Example plugin report:
Example plugin unload:
Example csearch invocation (completion management):
Example compile invocation:
Example create invocation:
Installation
Execute:
sh -c "$(curl -fsSL https://raw.githubusercontent.com/psprint/zplugin/master/doc/install.sh)"
To update run the command again (or just execute doc/install.sh) or run zplugin self-update.
Zplugin will be installed into ~/.zplugin/bin. .zshrc will be updated with
three lines of code that will be added to the bottom (the lines will be sourcing
zplugin.zsh and setting up completion).
Completion will be available, for command zplugin and aliases zpl, zplg.
After installing and reloading shell give Zplugin a quick try with zplugin help.
Manual installation
To manually install Zplugin clone the repo to e.g. ~/.zplugin/bin:
mkdir ~/.zplugin
git clone https://github.com/psprint/zplugin.git ~/.zplugin/bin
and source it from .zshrc (above compinit):
source ~/.zplugin/bin/zplugin.zsh
If you place the source below compinit, then add those two lines after the source:
autoload -Uz _zplugin
(( ${+_comps} )) && _comps[zplugin]=_zplugin
After installing and reloading shell give Zplugin a quick try with zplugin help.
Compilation
It's good to compile zplugin into Zsh bytecode:
zcompile ~/.zplugin/bin/zplugin.zsh
Zplugin will compile each newly downloaded plugin. You can clear compilation of
a plugin by invoking zplugin uncompile {plugin-spec}. There are also commands
compile, compiled that control the functionality of compiling plugins.
Usage
% zpl help
Usage:
-h|--help|help - usage information
man - manual
self-update - updates Zplugin
load {plugin-name} - load plugin
light {plugin-name} - light plugin load, without reporting
unload {plugin-name} - unload plugin
snippet [-f] [--command] {url} - source (or add to PATH with --command) local or remote file (-f: force - don't use cache)
update {plugin-name} - Git update plugin (or all plugins and snippets if --all passed)
status {plugin-name} - Git status for plugin (or all plugins if --all passed)
report {plugin-name} - show plugin's report (or all plugins' if --all passed)
loaded|list [keyword] - show what plugins are loaded (filter with `keyword')
cd {plugin-name} - cd into plugin's directory
create {plugin-name} - create plugin (also together with Github repository)
edit {plugin-name} - edit plugin's file with $EDITOR
glance {plugin-name} - look at plugin's source (pygmentize, {,source-}highlight)
stress {plugin-name} - test plugin for compatibility with set of options
changes {plugin-name} - view plugin's git log
recently [time-spec] - show plugins that changed recently, argument is e.g. 1 month 2 days
clist|completions - list completions in use
cdisable {cname} - disable completion `cname'
cenable {cname} - enable completion `cname'
creinstall {plugin-name} - install completions for plugin
cuninstall {plugin-name} - uninstall completions for plugin
csearch - search for available completions from any plugin
compinit - refresh installed completions
dtrace|dstart - start tracking what's going on in session
dstop - stop tracking what's going on in session
dunload - revert changes recorded between dstart and dstop
dreport - report what was going on in session
dclear - clear report of what was going on in session
compile {plugin-name} - compile plugin (or all plugins if --all passed)
uncompile {plugin-name} - remove compiled version of plugin (or of all plugins if --all passed)
compiled - list plugins that are compiled
To use themes created for Oh-My-Zsh you might want to first source the git library there:
zplugin snippet 'http://github.com/robbyrussell/oh-my-zsh/raw/master/lib/git.zsh'
Then you can use the themes as snippets (zplugin snippet {file path or Github URL}).
Some themes require not only
Oh-My-Zsh's git library, but also git plugin (error about function current_branch appears).
Source it as snippet directly from Oh-My-Zsh:
zplugin snippet 'https://github.com/robbyrussell/oh-my-zsh/raw/master/plugins/git/git.plugin.zsh'
Such lines should be added to .zshrc. Snippets are cached locally, use -f option to download
a fresh version of a snippet.
Most themes require promptsubst option (setopt promptsubst in zshrc), if it isn't set prompt
will appear as something like: $(build_prompt).
You might want to supress completions provided by the git plugin by issuing zplugin cdclear -q
(-q is for quiet) – see below Ignoring Compdefs.
To summarize:
zplugin snippet 'http://github.com/robbyrussell/oh-my-zsh/raw/master/lib/git.zsh'
zplugin snippet 'https://github.com/robbyrussell/oh-my-zsh/raw/master/plugins/git/git.plugin.zsh'
zplugin cdclear -q # <- forget completions provided up to this moment
setopt promptsubst
# Load theme
zplugin snippet 'https://github.com/robbyrussell/oh-my-zsh/blob/master/themes/dstufft.zsh-theme'
# Load plugin-theme depending on OMZ git library
zplugin light NicoSantangelo/Alpharized
Calling compinit
Compinit should be called after loading of all plugins and before possibly calling cdreply.
Zplugin takes control over completions, symlinks them to ~/.zplugin/completions and adds
this directory to $FPATH. You manage those completions via commands starting with c:
csearch, clist, creinstall, cuninstall, cenable, cdisable.
All this brings order to $FPATH, there is only one directory there.
Also, plugins aren't allowed to simply run compdefs. You can decide whether to run compdefs
by issuing zplugin cdreplay (compdef-replay). To summarize:
source ~/.zplugin/bin/zplugin.zsh
zplugin load "some/plugin"
...
zplugin load "other/plugin"
autoload -Uz compinit
compinit
zplugin cdreplay -q # -q is for quiet
This allows to call compinit once.
Performance gains are huge, example shell startup time with double compinit: 0.980 sec, with
cdreplay and single compinit: 0.156 sec.
Ignoring Compdefs
If you want to ignore compdefs provided by some plugins or snippets, place their load commands
before commands loading other plugins or snippets, and issue zplugin cdclear:
source ~/.zplugin/bin/zplugin.zsh
zplugin snippet https://github.com/robbyrussell/oh-my-zsh/blob/master/plugins/git/git.plugin.zsh
zplugin cdclear -q # <- forget completions provided up to this moment
zplugin load "some/plugin"
...
zplugin load "other/plugin"
autoload -Uz compinit
compinit
zplugin cdreplay -q # <- execute compdefs provided by rest of plugins
zplugin cdlist # look at gathered compdefs
Non-Github (local) plugins
Use create command with user name _local (the default) to create plugin's
skeleton. It will be not connected with Github repository (because of user name
being _local). To enter the plugin's directory use cd command with just
plugin's name (without _local).
The special user name _local is optional also for other commands, e.g. for
load (i.e. zplugin load myplugin is sufficient, there's no need for
zplugin load _local/myplugin).
IRC channel
Simply connect to chat.freenode.net:6697 (SSL) or chat.freenode.net:6667 and join #zplugin.









