Closed yingzhu146 closed 3 years ago
I can't reproduce this with the steps below, but I've left them since you said not to delete them 😄
You telling me that in itself is useful info. Now I know that at least you tried it. Before I added that notice, many people would simply immediately delete those steps, without even trying them. 🙂
When you launch a new kitty tab via kitty's remote control, can you try starting Zsh with zsh -vx
? Then please paste the output here so I can have a look where it fails.
Thanks a lot for having a look here, really appreciate you taking your time!
I hope I understood you correctly since I'm executing zsh twice, I replaced the second one with -xv
@yingzhu146 I don't see any error messages in the output you posted. Please disable Powerlevel9k/Powerlevel10k (it generates too much spam), then do the same thing I asked you (zsh -vx
), but don't stop before you see an error.
Yep sorry for the delay:
It looks like your $_comp_dumpfile
(/Users/yingzhu/.zcompdump-MacBook Air (3)-5.8
) is strangely enough pretty much empty. Can you delete it and then try again?
Again sorry for being slow
I rm $_compdumpfile
@yingzhu146 It looks like you're not using the latest commit in the main
branch. Can you please do the following and then try again?
$ cd ~zsh-autocomplete
$ git switch main # Make sure you test with the `main` branch.
$ git pull # Update to the latest commit.
@marlonrichert looks like its fixed in main 🥳 I don't see the errors anymore - thanks a ton!
@yingzhu146 See, this is another reason why you should always follow the bug template. 😉
PS: If you use my software on a regular basis, please consider leaving a tip. 🙂
zsh-autocomplete
version: 7e038790c32676ac46090870f1036abd65f10c98The plugin works perfectly in my normal shell, however, when I use it inside a terminal emulator of e.g. neovim or launch
zsh
with command (zsh -ci
) in a new kitty tab via kitty's remote control (/opt/homebrew/bin/kitty @ --to unix:/tmp/mykitty launch --type=tab --copy-env zsh -c 'cd ~/; zsh -i'
) I get the above. It sounds to me that this should be due to the shell environment, but sourcing within.zshenv
vszshrc
doesn't work and the error messages are very cryptic to me so not sure how to best debug.I can't reproduce this with the steps below, but I've left them since you said not to delete them 😄