Skip to content
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

Distinguish Between Array and Path Series Inputs in Fish Shell #162

Open
5 of 9 tasks
razvanazamfirei opened this issue Nov 10, 2023 · 0 comments · May be fixed by #163
Open
5 of 9 tasks

Distinguish Between Array and Path Series Inputs in Fish Shell #162

razvanazamfirei opened this issue Nov 10, 2023 · 0 comments · May be fixed by #163
Labels
bug Something isn't working

Comments

@razvanazamfirei
Copy link

Please verify the following:

Xshe Version

0.5.1

Current Behavior

Passing arrays in fish shell with xshe defaults to treating them as a path series due to the automatic addition of the --path argument.

Expected Behavior

The shell script should be able to differentiate between an array intended as a series of paths and a regular array. Users should be able to pass a regular array without the script automatically considering it as a path series.

Steps To Reproduce

  1. Use xshe to set an environment variable as an array in the fish shell.
  2. Observe that the array is treated as a path series rather than a simple array.
❯ echo "XDG_DATA_DIRS   = ['element_1', 'element_2']" | xshe --pipe fish
set -gx --path XDG_DATA_DIRS 'element_1':'element_1'

Which operating systems are affected?

  • macOS
  • Windows
  • Linux

Which shells does this affect?

  • Bash
  • Zsh
  • Fish

Anything else?

No response

@razvanazamfirei razvanazamfirei added the bug Something isn't working label Nov 10, 2023
@razvanazamfirei razvanazamfirei linked a pull request Nov 10, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant