Prezto: ssh hosts suggestions doesn't work for Manjaro latest update

Created on 16 Apr 2018  路  16Comments  路  Source: sorin-ionescu/prezto

Description

ssh hosts suggestions doesn't work for Manjaro latest update.
Reverting zsh package to zsh-5.4.2-2-x86_64.pkg.tar.xz fixes this problem. I also have Antergos(also Arch derivative) system and this system also have the same issue with 5.5 version of zsh.

ssh _alternative:69: command not found: _ssh_hosts
_alternative:69: command not found: _ssh_hosts
_alternative:69: command not found: _ssh_hosts

screenshot_20180416_123647

Expected behavior

No errors and suggested hosts appear.

Actual behavior

Some errors printed and no suggested hosts.

Steps to Reproduce

  1. Type ssh and press Tab Tab for host suggestion

Versions

  • Prezto commit: 300102897a4710e1559e4435c686f794d126d3c3
  • ZSH version: 5.5
  • OS information:
    System: Host: DzirT-LT Kernel: 4.9.94-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.12.4
    Distro: Manjaro Linux 17.1.8 Hakoila
Bug

Most helpful comment

I haven't been able to reproduce this on a fresh arch install in a VM. Maybe it's related to the completion cache? You can test this by removing ~/.zcompdump and opening a new shell.

All 16 comments

Thanks for filing this! Unfortunately it looks like it is almost definitely a Manjaro issue and not a prezto issue. It looks like even the completions we do bundle don't include one for the ssh command, so that's provided by your OS.

@belak thx for clarification. But as I stated above this issue reproducible for all Arch derivatives. It is not just Manjaro
And what package/command provides autocompletion so I will try search/install it?

I have been having this issue on a fresh archlinux installation as well. I can verify that if I configure zsh normally without prezto, ssh completion works fine. I don't know if I believe this is a 100% upstream issue.

Edit: Strange thing is that my old machine that has been running zsh and prezto for ages is working fine, even after upgrading prezto to the latest commit from master. Probably is something funny going on making this neither fully one or the other. I'll see if I can figure out anything else helpful later when I have more time.

Thanks for following up. I've reopened the issue and tagged it as a bug.

I'm having the same problem with my zsh setup on archlinux using zsh v5.5 with prezto. A friend of mine got the same problem with his arch and zsh v5.5 setup, but he's using another zsh config framework (https://github.com/zimfw/zimfw I think is his base).

This commit in zsh removes a function with the same name as this error message spits out, and moves it to a separate file. (I'm not very familiar with the code base and/or the programming languages in use, so I'm not sure if this is a problem.)

(Sorry if this just adds noise, just adding something I found while trying to find out what's wrong.)

I haven't been able to reproduce this on a fresh arch install in a VM. Maybe it's related to the completion cache? You can test this by removing ~/.zcompdump and opening a new shell.

That makes perfect sense! And..... look at that, it worked. Thanks @belak!

@tsabirgaliev @sklirg Are you still seeing this issue after clearing the completion cache? It should automatically when you open the shell after 20 hours, but you can remove ~/.zcompcache to manually clear it.

I'm not sure @belak, probably you mis-mentioned me?

Yeah, my mistake. I think I meant @IevgenSobko. Sorry about that.

@belak On Manjaro it doesn't help.
screenshot_20180421_095558

On Antergos I reverted zsh few days ago and today after your comments updated back to verify this and for some reason it started working even without clearing zshatocompletion folder

Removing ~/.zcompcache solved the problem for me on archlinux with zsh 5.5.1. :+1:

@IevgenSobko It looks like we use 2 cache files (I only mentioned one of those before) .zcompdump and .zcompcache. If you remove both of those and start a new shell, do you still see the error?

@belak your latest hint with removing both files helped me.
Thanks for you patience. Closing this issue.

Thanks for following up! I'm glad it was a simple fix, though I wish it was easier to automate.

Removing .zcompdump worked for me

Was this page helpful?
0 / 5 - 0 ratings

Related issues

belak picture belak  路  4Comments

mischaboldy picture mischaboldy  路  3Comments

gdetrez picture gdetrez  路  5Comments

lokesh-krishna picture lokesh-krishna  路  5Comments

michaelaye picture michaelaye  路  4Comments