You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows 10, using Git Bash, after the regular setup, the autocompletion outputs the following message:
$ platform bash: C:UsersIEUser.platformshbinplatform: command not found
It seems that the \ character is stripped in the path.
Having a look at the generated autocompletion.sh, I figured out that the path to the platform CLI is not quoted, and the \ are not doubled.
After this change, and after sourcing ~/.bashrc, the autocompletion works.
It ouputs another error, but probably related to the Windows Bash implementation:
__ltrim_colon_completions: command not found
The text was updated successfully, but these errors were encountered:
lolautruche
added a commit
to lolautruche/platformsh-cli
that referenced
this issue
Oct 26, 2022
Add quotes around the application executable before passing it to the autocomplete hook script.
Quoting prevents issues with the path when containing special characters (WS and/or `\`).
On Windows 10, using Git Bash, after the regular setup, the autocompletion outputs the following message:
It seems that the
\
character is stripped in the path.Having a look at the generated
autocompletion.sh
, I figured out that the path to theplatform
CLI is not quoted, and the\
are not doubled.I was able to fix the issue by replacing:
RESULT=$(C:\Users\IEUser\.platformsh\bin\platform _completion --shell-type bash >/dev/null)
by:
RESULT=$("C:\Users\IEUser\.platformsh\bin\platform" _completion --shell-type bash >/dev/null)
After this change, and after sourcing
~/.bashrc
, the autocompletion works.It ouputs another error, but probably related to the Windows Bash implementation:
The text was updated successfully, but these errors were encountered: