Re: printf %q ~ not escaped?

[Chet Ramey]

On 2/22/12 2:47 AM, John Kearney wrote:
 Bash Version: 4.2
 Patch Level: 10
 Release Status: release
 
 Description:
 printf %q ~ not escaped?
 
 which means that this
 eval echo $(printf %q ~)
 results in your home path not a ~
 unlike
 eval echo $(printf %q *)
 
 as far as I can see its the only character that isn't treated as I
 expected.

Thanks for the report.  This will be fixed in the next bash release.



-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

printf %q ~ not escaped?

[John Kearney]

Bash Version: 4.2
Patch Level: 10
Release Status: release

Description:
printf %q ~ not escaped?

which means that this
eval echo $(printf %q ~)
results in your home path not a ~
unlike
eval echo $(printf %q *)

as far as I can see its the only character that isn't treated as I
expected.