-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to use ~/ as path to file #336
Comments
The auto-completion script is generated by the CLI framework that we're using, so we don't have direct control over the contents. We'd need to wait for a patch (or contribute a patch ourselves). @wtfacoconut Can you please confirm this issue, and then report this on the picocli issues page? Of course, if you can develop a patch, that would be even better. |
Hey @xakrurychle , it's somewhat clear that you're doing this from some kind of *nix shell. Can you detail which OS and shell you're running fcli from? Also, when you say "autocompletion", are you saying that you're running the command |
$ $SHELL --version $ cat /etc/os-release CENTOS_MANTISBT_PROJECT="CentOS-7"
What I mean by autocompletion is the latter you mention. Using |
Being a Java application, fcli doesn't support Potentially we could manually implement If we choose to implement support for |
The reason for raising this is because I use fortifyclient on daily basis and using FCLI as a successor with extended options and possibilities, the absence of tabbing feature for |
Further research leads to remkop/picocli#437 (comment), describing how to have any I've opened a new picocli issue to request input on this issue: remkop/picocli#2068 As a side node, filename auto-completion only seems to be applicable to options or parameters declared as |
Further research shows that this issue only affects positional parameters; completion candidates are correctly shown when |
fcli ssc appversion-artifact upload ~/here.fpr --appversion ::myFCLICreatedVersion::
Autocompletion for the upload option does not work with ~/xyz but works with /home/user/xyz
The text was updated successfully, but these errors were encountered: