[Bug 213474] sed behavior change with a/i/c operands.

2017-03-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 Sergey changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 213474] sed behavior change with a/i/c operands.

2016-11-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 --- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: pfg Date: Wed Nov 9 18:00:50 UTC 2016 New revision: 308472 URL: https://svnweb.freebsd.org/changeset/base/308472 Log: MFC r308314: sed(1): add LEGAC

[Bug 213474] sed behavior change with a/i/c operands.

2016-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 --- Comment #7 from Sergey --- IMHO it'd be better to leave BSD behavior as default one as anyone who likes may install GNU sed from ports (/usr/ports/textproc/gsed) together with GNU awk and bash to play with. -- You are receiving this m

[Bug 213474] sed behavior change with a/i/c operands.

2016-11-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 --- Comment #6 from Pedro F. Giffuni --- (In reply to commit-hook from comment #5) For the record: kib@ has suggested, and I agree, that an environment variable may be more convenient for this case. IMHO, the default should remain the cur

[Bug 213474] sed behavior change with a/i/c operands.

2016-11-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: pfg Date: Fri Nov 4 20:49:59 UTC 2016 New revision: 308314 URL: https://svnweb.freebsd.org/changeset/base/308314 Log: sed(1): add LEGACY_BSDSED_COMPAT

[Bug 213474] sed behavior change with a/i/c operands.

2016-10-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 --- Comment #4 from Sergey --- (In reply to Pedro F. Giffuni from comment #3) In my humble opinion it's a bad decision. In that case i'd rather patch sed's source like this: # Restore original BSD sed sed -E -i '' \

[Bug 213474] sed behavior change with a/i/c operands.

2016-10-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 Mark Linimon changed: What|Removed |Added Keywords||patch -- You are receiving this ma

[Bug 213474] sed behavior change with a/i/c operands.

2016-10-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 Pedro F. Giffuni changed: What|Removed |Added Attachment #175892|0 |1 is obsolete|

[Bug 213474] sed behavior change with a/i/c operands.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 --- Comment #2 from Pedro F. Giffuni --- Created attachment 175892 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175892&action=edit Proof-of-concept: provide a compile-time flag for GNU compatibility An idea that could use poli

[Bug 213474] sed behavior change with a/i/c operands.

2016-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 Pedro F. Giffuni changed: What|Removed |Added Summary|sed behaviuor with a/i/c|sed behavior change with