You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing Heroku CLI Autocomplete by running heroku autocomplete and following the install instructions, a .zcompdump file will be created at $ZDOTDIR every time .zshrc is run, or at $HOME if $ZDOTDIR is not set.
This is because no -d option is given in ~/Library/Caches/heroku/autocomplete/zsh_setup (macOS), which is a file that is created by create.ts when running heroku autocomplete.
Do you want to request a feature or report a bug?
This is a bug report.
heroku/7.59.2 darwin-x64 node-v12.21.0
macOS Monterey 12.2.1
What is the current behavior?
After installing Heroku CLI Autocomplete by running
heroku autocomplete
and following the install instructions, a.zcompdump
file will be created at$ZDOTDIR
every time.zshrc
is run, or at$HOME
if$ZDOTDIR
is not set.This is because no
-d
option is given in~/Library/Caches/heroku/autocomplete/zsh_setup
(macOS), which is a file that is created bycreate.ts
when runningheroku autocomplete
.cli/packages/autocomplete/src/commands/autocomplete/create.ts
Lines 228 to 229 in 67b9080
What is the expected behavior?
If the environment variable
$ZSH_COMPDUMP
is set, the.zcompdump
file should be created there instead of$ZDOTDIR
or$HOME
.So if
$ZSH_COMPDUMP
exists,compinit -d "$ZSH_COMPDUMP";
should run instead of justcompinit;
.A potential implementation for a fix would be replacing line 229 in with the following check:
This would not change any behavior for anyone without
$ZSH_COMPDUMP
set, and respects$ZSH_COMPDUMP
for those who do.The text was updated successfully, but these errors were encountered: