-
Notifications
You must be signed in to change notification settings - Fork 7
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
Execution of shell-completion causes change in console IFS
value
#2
Comments
Thanks for the bugreport. Indeed that shouldn't be the case, and hopefully I can just fix it by using local, too |
Closed
3 tasks
Setting local works, but beware of autocompletions, other autocompletions may call. So
to
seems to work |
alexiswl
added a commit
to umccr/ica-ica-lazy
that referenced
this issue
Oct 7, 2022
Stops IFS being set in environment. Solves: * perlpunk/shell-completions#2 * scop/bash-completion#515
alexiswl
added a commit
to umccr/cwl-ica-cli
that referenced
this issue
Oct 7, 2022
Stops IFS being set in environment. Solves: * perlpunk/shell-completions#2 * scop/bash-completion#515
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I have an example yaml and output bash script from running the
appspec completion
command with the--bash
parameter.Command run
Click to expand!
The bash script is sourced in my
~/.bash_profile
.Example yaml file
Click to expand!
Example bash completion script
Click to expand!
If I run the following command on a new console:
But I then call the auto-completion script
I get a different value when trying to get the IFS output
I am running through WSL2 and this hasn't caused me any troubles, however, any colleague that runs bash on MacOS and then installs autocompletion with
brew install bash_completion@2
ends up with the following issue: scop/bash-completion#515Is there a way for IFS to be reset to the default after the completion script has been activated?
Work around has been to run
brew install bash_completion@2 --HEAD
since scop/bash-completion#515 has been resolved by scop/bash-completion#519The text was updated successfully, but these errors were encountered: