Re: are head/tail allowed (required?) to rewind stdin

2018-04-30 Thread Stephane Chazelas
2018-04-30 16:49:34 +0100, Geoff Clare: [...] > Yes, but it clearly shows that this offset is intended to be honoured > by the next utility to read from stdin, when it says: > > tail -n +2 file > (sed -n 1q; cat) < file > [...] > The second command is equivalent to the first only

Re: are head/tail allowed (required?) to rewind stdin

2018-04-30 Thread Geoff Clare
Stephane Chazelas wrote, on 30 Apr 2018: > > 2018-04-30 15:50:10 +0100, Geoff Clare: > > Stephane Chazelas > > wrote, on 30 > > Apr 2018: > > > > > > The head/tail specifications refer to line/byte offsets

Re: are head/tail allowed (required?) to rewind stdin

2018-04-30 Thread Stephane Chazelas
2018-04-30 15:50:10 +0100, Geoff Clare: > Stephane Chazelas > wrote, on 30 Apr 2018: > > > > The head/tail specifications refer to line/byte offsets as > > offsets within *files* as opposed to *input*. > > > > Does it mean that: > > >

Re: are head/tail allowed (required?) to rewind stdin

2018-04-30 Thread Geoff Clare
Stephane Chazelas wrote, on 30 Apr 2018: > > The head/tail specifications refer to line/byte offsets as > offsets within *files* as opposed to *input*. > > Does it mean that: > > { head -n 1; head -n 1; } < file > { tail -n 1; tail -n 1; } < file > > are required

Re: Pushing/restoring a file descriptor for a compound command

2018-04-30 Thread Chet Ramey
On 4/27/18 9:53 PM, Martijn Dekker wrote: > That's what I've got. Is that a sane interpretation? > > It would be nice if there were something more unequivocal in the standard, > but it seems there isn't... > >> You might have more luck with bash (perhaps.) > > Chet, what do you think? There's

[1003.1(2016)/Issue7+TC2 0001105]: problems with backslashes in awk strings and EREs

2018-04-30 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1105 == Reported By:stephane Assigned To:

[1003.1(2016)/Issue7+TC2 0001105]: problems with backslashes in awk strings and EREs

2018-04-30 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1105 == Reported By:stephane Assigned To:

[1003.1(2016)/Issue7+TC2 0001105]: problems with backslashes in awk strings and EREs

2018-04-30 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1105 == Reported By:stephane Assigned To:

are head/tail allowed (required?) to rewind stdin

2018-04-30 Thread Stephane Chazelas
Hello, The head/tail specifications refer to line/byte offsets as offsets within *files* as opposed to *input*. Does it mean that: { head -n 1; head -n 1; } < file { tail -n 1; tail -n 1; } < file are required to print the first/last line of "file" twice (assuming "file" is seekable and is not

[1003.1(2016)/Issue7+TC2 0001105]: problems with backslashes in awk strings and EREs

2018-04-30 Thread Austin Group Bug Tracker
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1105 == Reported By:stephane Assigned To:

Re: Minutes of the 26th April 2018 Teleconference

2018-04-30 Thread Geoff Clare
Robert Elz wrote, on 27 Apr 2018: > > This is kind of odd... > > | Attendees: > | Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR > | Joerg Schilling, FOKUS Fraunhofer > [...] > > | We deferred bugs 1084, 1085 and 1100 until Joerg is on the call. > > It looks