I'm not sure whether this will help, but have a look at Important Nodes About Dealing with SSH and Pseudo-Termials in the module's docs.
What you're trying to do is trigger the shell's autocompletion, which is very dependent on the shell, for example bash has Programmable Completion, but it's up to the vendor to distribute the scripts that feed this functionality, for example Debian-based systems have the package bash-completion that contains a very complex set of scripts. You'll probably see differences in the autocompletion from version to version, and very likely from vendor to vendor. Using this in an automated fashion is likely not going to be very robust.
This seems to me like it might be an XY Problem. What exactly are you trying to figure out via the shell completion? If you want to know if a certain program is somewhere in the PATH, try which.
In reply to Re: checking command suggestions with Net::SSH::Expect
by haukex
in thread checking command suggestions with Net::SSH::Expect
by himanshu.chauhan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |