Forum Discussion
cjunior
Dec 08, 2015Nacreous
Hi,
I can't say it is a bug, but it seems that the curly braces doesn't have the same behavior on the replacement string as to hex codes in the search string. Thereby, it should work by removing curly braces because this prevents command execution and variable expansion.e.g.
it should work:
@\x3Chttp@\x17http@
@$search@$replace@
it shouldn't work:
{@\x3Chttp@\x17http@}
{@$search@$replace@}