*.exe
support in ziextract
is is actually Firefox installer support, experimental proof of concept to introduce a more versatile support later.. This is what makes pack for firefox
on windows work
btw, how did you enable this log output?+→zinit-extract:1> chmod a+x -- ./docker-compose-windows-x86_64.exe +→zinit-extract:2> cygpath -w /home/srivastavaan/.local/share/zinit/plugins/docker---compose +→zinit-extract:2> ./docker-compose-windows-x86_64.exe /S '/D=E:\scoop\apps\msys2\2022-06-03\home\srivastavaan\.local\share\zinit\plugins\docker---compose'
+→zinit-extract:1> chmod a+x -- ./docker-compose-windows-x86_64.exe
+→zinit-extract:2> cygpath -w /home/srivastavaan/.local/share/zinit/plugins/docker---compose
+→zinit-extract:2> ./docker-compose-windows-x86_64.exe /S '/D=E:\scoop\apps\msys2\2022-06-03\home\srivastavaan\.local\share\zinit\plugins\docker---compose'
exec zsh -x
@turboBasic
zsh -icx "zinit for id-as'age' as'program' from'gh-r' ver'latest' pick'age/*' @FiloSottile/age"
xecho -e "\n--- $(which nvim)\n" ;zi delete neovim/neovim -y; echo -e "--- $(which nvim)\n\n";
zi for \
from'gh-r' \
nocompile \
nocompletions \
sbin'!**/nvim -> nvim' \
ver'nightly' \
@neovim/neovim;
echo -e "\n\n--- $(which nvim)\n---- $(nvim --version)"
echo -e "\n\n--- $(which nvim)\n\n" ;zi delete neovim/neovim -y; echo -e "\n\n--- $(which nvim)\n\n";
zi for \
from'gh-r' \
nocompile \
nocompletions \
lbin'!**/nvim -> nvim' \
ver'nightly' \
@neovim/neovim;
echo -e "\n\n--- $(which nvim)\n\n---- $(nvim --version)"
zinit ice from'gh-r' nocompile lbin'!**/nvim -> nvim'
zinit load @neovim/neovim
@kmath313 np, happy to help.
That behavior is confuses me too. I think there is a open PR that might fix this issue. On the other hand, I’ve hit the same exact issue trying you brought up, but didn’t realize it worked if ran interactively.
So TLDR; the expected behavior is to have same behavior across interactive and scripted zi commands. I’ll check this against the open PR to see if it fixes it.
@Stefanqn Could you open an issue?
https://github.com/zdharma-continuum/zinit-annex-bin-gem-node/issues/new/choose
.zwc
files in my $FAST_WORK_DIR
, is there any doc about what are those?
zinit ice wait lucid atinit"ZPLGM[COMPINIT_OPTS]=-C; zpcompinit; zpcd replay"
rustup completions zsh
gh
, or gh-r
? I'm trying to get this https://downloads.dockerslim.com/releases/1.39.0/dist_linux_arm64.tar.gz
I'm wondering if anybody else has issues with yank-pop. It doesn't work more than once for me. It seems a similar issue has been described (and apparently fixed) in this zsh-users/zsh-syntax-highlighting#183.
The issue does not persist if I switch to zsh-syntax-highlighting.
To update, run :
zi self-update
zi compinit
Note: compinit
call is needed to refresh the auto-completion.
grh
, my alias for 'git reset', and my history showed 'grhh', the alias for 'git reset --hard'. See above for an example.zinit as'program' bpick'lfs_2.6.0.zip' from'gh-r' for '@Canop/lfs'
results in "r: failed to find the correct GitHub release asset to download, modify bpick-ICE (current bpick: lfs_2.6.0.zip)." Same for zini for from"gh-r" lbin"jq-* -> jq" stedolan/jq
lbin
and local reference snippet format, when I do zi update
(to update all) I got the following messages. Everything still works fine though. Just want to know if there's a better way to hanle the situation.zinit ice id-as"ngoc-prompt" nocompile; zinit snippet $HOME/.zsh/themes/ngoc.zsh
zinit as"null" wait"0a" lucid light-mode from"gh-r" lbin"!" lman completions for \
lbin"!**/rg" BurntSushi/ripgrep
Updating snippet: themes/ngoc.zsh... (identified as: ngoc-prompt)
realpath: illegal option -- -
usage: realpath [-q] [path ...]
Linking ngoc-prompt...
/Users/ngoc/.local/share/zinit/snippets/ngoc-prompt/ngoc-prompt -> /Users/ngoc/.zsh/themes/ngoc.zsh
Note: updating also unloaded plugins
Updating BurntSushi/ripgrep
Binary release already up to date (version: 13.0.0)
[linkbin annex] Re-created the rg soft link however the rg binary does not exist or failed to set +x on it
@ngocphamm I assume you are on a mac. The error is due to macOS, a fork of BSD, having relativley old and inconsistent coreutils (in comparision to GNU.
See the history of the MacOS and original Mach project. It is interesting.
You can fix this via:
# see what coreutils installs
brew info coreutils
# install
brew install gnu-coreutils
Bug reproduced below:
The following .zshrc outputs command not found: compdef
. It seems that compdef substitution does not work. Does anyone know why ?
ZINIT_HOME="${XDG_DATA_HOME:-${HOME}/.local/share}/zinit/zinit.git"
source "${ZINIT_HOME}/zinit.zsh"
zinit ice lucid from"gh-r" bpick"fd-*-darwin*" as"program" pick"fd*/fd"
zinit light sharkdp/fd
compdef _gnu_generic fd
autoload -Uz compinit
compinit
zinit cdreplay -q
I use the following versions.
$ zinit version
zinit v3.9.0-26-gf214ebe4 (darwin21.0_arm64)
$ zsh --version
zsh 5.8.1 (x86_64-apple-darwin21.0)
You can install the fd
completion via:
zinit for id-as"fd/_fd" as"completion" is-snippet light-mode \
https://raw.githubusercontent.com/sharkdp/fd/master/contrib/completion/_fd
Tangential, but you don't need bpick
zinit for light-mode from'gh-r' lbin'!' null id-as @sharkdp/fd
Also, I saw you have this:
zinit ice wait lucid from"gh-r" as"program" pick"ripgrep*/rg" \
atclone"ln -sf ${ZINIT_HOME}/plugins/BurntSushi---ripgrep/ripgrep-*/doc/rg.1 ${ZINIT_HOME}/man/man1" \
atpull"%atclone"
zinit light BurntSushi/ripgrep
if you install binary-symlink
and link-man
annexes
zinit light-mode for @zdharma-continuum/zinit-annex-{linkman,binary-symlink}
can be simplified to:
zinit ice id-as'rg' as'null' lman lbin from"gh-r"
zinit light @BurntSushi/ripgrep