Indeed, it is more compact to report
' a' than
\ \ \ \ \ \ \ \ \ \ a
OK OK... see you next bug.
> > Well anyway, it would be 'no skin off of bash's back' if it just
> > reported what it was given.
It's the difference between what bash reads and its translation to an internal
form based on words. The words are then translated to an external form
with quoting added to make the original and ex
jida...@jidanni.org wrote:
Well anyway, it would be 'no skin off of bash's back' if it just
reported what it was given.
If it was given
' 'a b c
it should report
' 'a b c
and not just 'assume' we prefer
' a' b c
or
' a' 'b' 'c'
etc.
Just as legitimate and doesn't cause calls in the middle
Well anyway, it would be 'no skin off of bash's back' if it just
reported what it was given.
If it was given
' 'a b c
it should report
' 'a b c
and not just 'assume' we prefer
' a' b c
or
' a' 'b' 'c'
etc.
Just as legitimate and doesn't cause calls in the middle of the night
from the old fol
> "JS" == Jan Schampera writes:
JS> I'd say this is expected (and by the way it's not only on set -x).
I see. The spaces indeed get glued to the sides. OK, see ya next time.
jida...@jidanni.org wrote:
$ cat 201012contract
#!/bin/sh -eux
set a b c d e f
: ''$@''
: ' '$@' '
: ''$*''
: '' $* ''
: " "$* " "
$ ./201012contract
+ set a b c d e f
+ : a b c d e f
+ : ' a' b c d e 'f '
+ : 'a' b c d e 'f'
+ : '' a b c d e f ''
+ : ' a' b c
WITNESS for yourselves as the quotes invade the parameters, absconding
with the ones at the edges, when close enough.
$ cat 201012contract
#!/bin/sh -eux
set a b c d e f
: ''$@''
: ' '$@' '
: ''$*''
: '' $* ''
: " "$* " "
$ ./201012contract
+ set a b c d e f
+ : a b c d e f
+ : '
