Re: Assignment-like word shouldn't be subjected to tilde expansion in POSIX mode

From	"M. Nejat AYDIN" <mnaydin@yahoo.com>
Newsgroups	gnu.bash.bug
Subject	Re: Assignment-like word shouldn't be subjected to tilde expansion in POSIX mode
Date	2020-07-21 10:55 +0300
Message-ID	<mailman.273.1595318116.24492.bug-bash@gnu.org> (permalink)
References	<CAH7i3LqG=mnoiSbetxVdg3wqso5orGgMqQk70-UfJ=wcdf6uLQ@mail.gmail.com> <8ddc4816-f85e-97b3-5c51-9b55acdcaca5@case.edu> <9881b6b4-237f-ea61-d9fc-9c3f9f9ae4c3@yahoo.com>

Show all headers | View raw

On 7/19/20 1:04 AM, Chet Ramey wrote:
> On 7/18/20 1:38 AM, Oğuz wrote:
>> See:
>>
>>      $ set +k -o posix
>>      $ echo foo=~:~
>>      foo=~:/home/oguz
>>
>> If I'm not misreading the standard `foo=~:~' should be printed
>> verbatim, all shells I have except bash does so.
> 
> Thanks for the report. This one has been around since bash-3.1.

Also, shouldn't the tilde be expanded following
     $ echo ~:
? The colon terminates tilde-prefix in an assignment, but there is no
assignment involved here.

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Assignment-like word shouldn't be subjected to tilde expansion in POSIX mode "M. Nejat AYDIN" <mnaydin@yahoo.com> - 2020-07-21 10:55 +0300

csiph-web