[Help-bash] Email formatting error (was: Re: echo and environment variables)

[David Niklas]

Dear Mr. Gaston,
Your reply messages appear in the bash-help digest as email (>), quoted
text. I think that this is an error on your end so I'm sending this
message just to you.
Below is a reply of yours with all headers attached. Notice that the URL
is double email quoted when it should be single email quoted.
This makes you especially difficult to follow when you do an inline reply.

Thanks,
David

Message: 2
Date: Thu, 5 Oct 2017 20:33:29 +0300
Subject: Re: [Help-bash] echo and environment variables
Content-Type: text/plain; charset="UTF-8"

Hi,
I'm a bit surprised: Can anyone tell why
$ xxx=hiho echo $xxx # xxx is only set for the current command
prints an empty line, while
$ xxx=hiho; echo $xxx; unset xxx # please note the semicolon!
prints
hiho
as expected?
see http://mywiki.wooledge.org/BashFAQ/104

[Pierre Gaston]

Thanks, I checked other replies I made and most seem fine, I guess I'll try
to pay a little extra attention.

Post by David Niklas
Dear Mr. Gaston,
Your reply messages appear in the bash-help digest as email (>), quoted
text. I think that this is an error on your end so I'm sending this
message just to you.
Below is a reply of yours with all headers attached. Notice that the URL
is double email quoted when it should be single email quoted.
This makes you especially difficult to follow when you do an inline reply.
Thanks,
David

Message: 2
Date: Thu, 5 Oct 2017 20:33:29 +0300
Subject: Re: [Help-bash] echo and environment variables

gmail.com>

Content-Type: text/plain; charset="UTF-8"

Hi,
I'm a bit surprised: Can anyone tell why
$ xxx=hiho echo $xxx # xxx is only set for the current command
prints an empty line, while
$ xxx=hiho; echo $xxx; unset xxx # please note the semicolon!
prints
hiho
as expected?
see http://mywiki.wooledge.org/BashFAQ/104