search

wting / autojump

A cd command that learns - easily navigate directories from the command line
Other
16.18k stars 705 forks source link

Error prompt when using with zsh #392

Open lookforit opened 8 years ago

lookforit commented 8 years ago

I installed autojump-zsh on Fedora 23. After launch zsh,it always says:

/etc/profile.d/autojump.bash:13: command not found: complete

I also tried install autojump MANUALLY,and added one line in .zshrc: [ -s ~/.autojump/etc/profile.d/autojump.sh ]] && . ~/.autojump/etc/profile.d/autojump.sh This time ,it gives me two line error prompt:

/etc/profile.d/autojump.bash:13: command not found: complete
/etc/profile.d/autojump.bash:52: = not found

Please tell me how to fix this?

psychoslave commented 8 years ago

did you find a solution? Same distro, same problem. Looking in every sourced filed documented http://how-to.wikia.com/wiki/Guide_to_linux_configuration_files and here https://wiki.archlinux.org/index.php/Zsh#Configuration_files adding echo, it looks like the autoujump.bash is sourced somewhere between the ~/.zshenv sourcing and the ~/.zshrc sourcing.

TomasTomecek commented 8 years ago

Hi, autojump comaintainer in Fedora here. Tried to reproduce the issue but didn't succeed. Looking at version of autojump in Fedora 23, it's quite old so I updated it to latest upstream release:

https://bodhi.fedoraproject.org/updates/autojump-22.3.0-1.fc23

It could fix the issue you are having. I tried it locally on my laptop and after putting

[[ -s /etc/profile.d/autojump.sh ]] && source /etc/profile.d/autojump.sh

to my ~/.zshrc, it worked just fine.

slhck commented 7 years ago

Getting the same error with v22.5.1, installed on Cygwin 2.8.0(0.309/5/3) via Babun:

/home/werner/autojump/share/autojump/autojump.bash:34: command not found: complete

I simply installed autojump by running the install.py script.

My ~/.zshrc contains:

[[ -s /home/werner/.autojump/etc/profile.d/autojump.sh ]] && source /home/werner/.autojump/etc/profile.d/autojump.sh

Apparently it misdetects the shell? Probably a different source of the problem.

cerebrux commented 4 years ago

This happened to me on a remote server when the account I was logged in was using but I was manually switching to zsh. To fix it, permanently switched the account to zsh and the error disappeared.

SteavenGamerYT commented 1 month ago

i still get this error