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

Unexpected behavior with set -a var "string" #31

Open
warptozero opened this issue Apr 11, 2024 · 0 comments
Open

Unexpected behavior with set -a var "string" #31

warptozero opened this issue Apr 11, 2024 · 0 comments

Comments

@warptozero
Copy link

Expected behavior in an interactive session:

> set cmd one two
> set -a cmd "three"
> set --show cmd
$cmd: set in global scope, unexported, with 3 elements
$cmd[1]: |one|
$cmd[2]: |two|
$cmd[3]: |three|

Observed behavior in an interactive session with pisces installed:

> set cmd one two
> set -a cmd "three"
> set --show cmd
$cmd: set in global scope, unexported, with 2 elements
$cmd[1]: |set -a cmd |
$cmd[2]: |three|

The command input was set -a cmd "three[enter]. When the closing" is also typed as in set -a cmd "three"[enter] the output is:

$cmd: set in global scope, unexported, with 2 elements
$cmd[1]: |set -a cmd "three"|
$cmd[2]: |three|

However when the complete line set -a cmd "three" is pasted in it works correctly.

I can reproduce this consistently on my system with fish version 3.7.1 in a fresh config directory with only jorgebucaran/fisher and laughedelic/pisces installed.

@warptozero warptozero changed the title Unexpected behavior with set -a "string" Unexpected behavior with set -a var "string" Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant