Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16596 > unrolled thread
| Started by | "M. Nejat AYDIN" <mnaydin@yahoo.com> |
|---|---|
| First post | 2020-07-21 10:55 +0300 |
| Last post | 2020-07-21 10:55 +0300 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | "M. Nejat AYDIN" <mnaydin@yahoo.com> |
|---|---|
| Date | 2020-07-21 10:55 +0300 |
| Subject | Re: Assignment-like word shouldn't be subjected to tilde expansion in POSIX mode |
| Message-ID | <mailman.273.1595318116.24492.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web