Date: Fri, 08 Aug 2014 17:29:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 160745] sed(1) appends '\n' at the end of binary data (unlike gsed(1)) Message-ID: <bug-160745-8-6dHuV4OECA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-160745-8@https.bugs.freebsd.org/bugzilla/> References: <bug-160745-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=160745 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: dumbbell Date: Fri Aug 8 17:29:02 UTC 2014 New revision: 269729 URL: http://svnweb.freebsd.org/changeset/base/269729 Log: sed(1): Don't force a newline on last line, if input stream doesn't have one While here, change how we check if the current line is the last one. Before, we just checked if there were more files after the current one. Now, we check the actual content of those files: they files may not have a line at all. This matches the definition of the "last line" by the Open Group. The new behavior is closer to GNU sed. PR: 160745 Phabric: https://phabric.freebsd.org/D431 Reviewed by: jilles Approved by: jilles Exp-run by: antoine Changes: head/usr.bin/sed/defs.h head/usr.bin/sed/main.c head/usr.bin/sed/process.c head/usr.bin/sed/tests/regress.y.out -- 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-160745-8-6dHuV4OECA>