Date: Sat, 22 Jul 2017 18:37:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220924] bsdgrep(1) unexpectedly stops processing command line arguments Message-ID: <bug-220924-8-bybxTvhLHT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220924-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220924-8@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=3D220924 --- Comment #3 from Kyle Evans <kevans@freebsd.org> --- I'll poke at the specifics later, but empty strings with grep(1) triggers a match-all behavior for what I assume are POSIX reasons. Empty patterns are = not valid EREs or BREs- just some grep specific behavior. My assumption at the moment is that we're just bailing out on the first file since it's a match-all. Not at a machine to test it at the moment, though. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220924-8-bybxTvhLHT>