Bug#605142: sed: incorrectly interprets \x hexadecimal escapes sometimes

2017-02-24 Thread Assaf Gordon
Hello, I've added a paragraph about the current behavior with your example to sed's manual: https://git.savannah.gnu.org/cgit/sed.git/commit/?id=a805d57e1f6427b55 regards, - assaf

Bug#605142: sed: incorrectly interprets \x hexadecimal escapes sometimes

2017-02-23 Thread Assaf Gordon
Hello, Picking up an old sed bug: Matija Nalis wrote: echo 'a^c' | sed -e 's/\x5e/b/' should produce output "abc" (as it does in "ssed" or "perl -pe"), but in GNU sed it produces "ba^c". I agree this is indeed GNU sed's behavior, but it's not clear it is incorrect behavior (or if there is

Bug#605142: sed: incorrectly interprets \x hexadecimal escapes sometimes

2010-11-27 Thread Matija Nalis
Package: sed Version: 4.2.1-7 Severity: normal If \x escape sequence in LHS resolves to some character which has special meaning in sed LHS (like ^, \, ...), GNU sed does not use it as hex-escaped, but instead as if it was literaly that character. For example: echo 'a^c' | sed -e 's/\x5e/b/'