Additional space at end of assignment in preexec's $2 and $3

Additional space at end of assignment in preexec's $2 and $3

[Daniel Hahler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

An assignment appears to have an additional " " at the end of $2 (and $3) in preexec:

    % preexec() { echo "== preexec =="; set -x; test $1 = $2; echo $3; set +x }
    % foo
    === preexec ==
    +preexec:0> test 'foo=' '=' 'foo= '
    +preexec:0> echo 'foo= '
    foo= 
    +preexec:0> set +x

Please note that 1="foo=", but 2 and 3 are "foo= ".


Regards,
Daniel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iD8DBQFUh3zvfAK/hT/mPgARAsqWAJ9bPMjZsKP+WLByg5hqTX9Zfq33FwCfUZR7
g7K0vki9ODKbLIm2prDVwVs=
=+Xau
-----END PGP SIGNATURE-----

Re: Additional space at end of assignment in preexec's $2 and $3

[Bart Schaefer]

On Dec 9, 11:51pm, Daniel Hahler wrote:
}
} An assignment appears to have an additional " " at the end of $2 (and
} $3) in preexec:

I believe that's because assignments by themselves are a special-case of
assignment-before-command, as far as the internal wordcode is concerned.

There is no guarantee that the user's input string and the other arguments
passed to preexec will be identical -- in fact, it's explicitly documented
that $2 will have been squashed down to a single line.

Here's a different example of whitespace changing:

torch% foo=bar    :
== preexec ==
+preexec:0> test 'foo=bar    :' '=' 'foo=bar :'
+preexec:0> echo 'foo=bar :'
foo=bar :
+preexec:0> set +x