Date: Sun, 07 Jun 2020 04:33:32 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 229925] [EXP-RUN] Disallow escaping ordinary characters in regex(3) Message-ID: <bug-229925-7788-gsHkErrMBp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229925-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-229925-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229925 --- Comment #27 from commit-hook@freebsd.org --- A commit references this bug: Author: kevans Date: Sun Jun 7 04:32:39 UTC 2020 New revision: 361884 URL: https://svnweb.freebsd.org/changeset/base/361884 Log: sed: attempt to learn about hex escapes (e.g. \x27) Somewhat predictably, software often wants to use \x27/\x24 among others = so that they can decline worrying about ugly escaping, if said escaping is e= ven possible. Right now, this software is using these and getting the wrong results, as we'll interpret those as x27 and x24 respectively. Some examp= les of this, when an exp-run was ran, were science/octopus and misc/vifm. Go ahead and process these at all times. We allow either one or two digi= ts, and the tests account for both. If extra digits are specified, e.g. \x27= 27, then the third and fourth digits are interpreted literally as one might expect. PR: 229925 MFC after: 2 weeks Changes: head/usr.bin/sed/compile.c head/usr.bin/sed/tests/sed2_test.sh --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229925-7788-gsHkErrMBp>