Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-12 Thread Bryan Drewery
On 3/8/2021 12:13 PM, Ed Maste wrote: > 5. Retire the special case for -I "". Just to be clear, we are not suggesting removing compat for -i '' right? -- Regards, Bryan Drewery ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mai

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-11 Thread Ed Maste
On Mon, 8 Mar 2021 at 16:41, Ed Maste wrote: > > On Mon, 8 Mar 2021 at 15:55, Ian Lepore wrote: > > > > I also hate the idea of requiring no space between -I and its related > > value. That seems like a huge POLA violation compared to how virtually > > every other command's options and argument

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread Ed Maste
On Mon, 8 Mar 2021 at 17:00, John-Mark Gurney wrote: > > How is the program suppose to tell when the extension is "-e", or -e > is a different option and not the argument to -I? -i-e is an in-place edit with extension "-e" -i -e is an in-place edit with no extension __

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread John-Mark Gurney
Ed Maste wrote this message on Mon, Mar 08, 2021 at 15:13 -0500: > A relatively minor but longstanding incompatibility between FreeBSD > and many other systems is the way sed handles backup files for > in-place editing -- sed's -I and -i options. GNU sed and other BSDs > accept an optional argument

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread Ed Maste
On Mon, 8 Mar 2021 at 15:55, Ian Lepore wrote: > > I also hate the idea of requiring no space between -I and its related > value. That seems like a huge POLA violation compared to how virtually > every other command's options and arguments work. On the other hand, -i.ext with no space is compati

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread Steffen Nurpmeso
Ian Lepore wrote in <8e9983a4243d158789029ec8b16837b35ca4451a.ca...@freebsd.org>: |On Mon, 2021-03-08 at 15:13 -0500, Ed Maste wrote: |> A relatively minor but longstanding incompatibility between FreeBSD |> and many other systems is the way sed handles backup files for |> in-place editing --

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread Ian Lepore
On Mon, 2021-03-08 at 15:13 -0500, Ed Maste wrote: > A relatively minor but longstanding incompatibility between FreeBSD > and many other systems is the way sed handles backup files for > in-place editing -- sed's -I and -i options. GNU sed and other BSDs > accept an optional argument: -I.bak will

Re: Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread Chris
On 2021-03-08 12:13, Ed Maste wrote: A relatively minor but longstanding incompatibility between FreeBSD and many other systems is the way sed handles backup files for in-place editing -- sed's -I and -i options. GNU sed and other BSDs accept an optional argument: -I.bak will save a backup file w

Rationalizing sed -i/-I (in-place editing) argument handling

2021-03-08 Thread Ed Maste
A relatively minor but longstanding incompatibility between FreeBSD and many other systems is the way sed handles backup files for in-place editing -- sed's -I and -i options. GNU sed and other BSDs accept an optional argument: -I.bak will save a backup file with a .bak extension, and -I with no ar