Updated Troubleshooting (markdown)
parent
c5ee8e7fc0
commit
587d1b9a62
1 changed files with 2 additions and 3 deletions
|
@ -2,16 +2,15 @@
|
|||
|
||||
If you are using the `completion` module, there can be a conflict if other scripts are running `compinit` too.
|
||||
|
||||
If you're getting a "warning: compinit being called again after completion module at ..." message in the terminal, then remove the `compinit` call from the mentioned file.
|
||||
In case you're getting a "warning: compinit being called again after completion module at ..." message in the terminal, then remove the `compinit` call from the mentioned file.
|
||||
|
||||
If you're getting a "warning: completion was already initialized before completion module." message in the terminal, then follow
|
||||
In case you're getting a "warning: completion was already initialized before completion module." message in the terminal, then follow
|
||||
these steps to check further:
|
||||
|
||||
1. Run the following code in your terminal, which will add lines to your `~/.zshenv` file:
|
||||
```zsh
|
||||
>>! ~/.zshenv <<\END
|
||||
autoload -Uz +X compinit
|
||||
functions[_original_compinit]=${functions[compinit]}
|
||||
functions[compinit]=$'print -u2 \'compinit being called at \'${funcfiletrace[1]}
|
||||
'${functions[compinit]}
|
||||
END
|
||||
|
|
Loading…
Reference in a new issue