BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1//
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20120311T02
RRULE:FREQ=YE
All
Enclosed are the minutes of the Monday meeting this week
regards
Andrew
---
Minutes of the 23rd March 2020 Teleconference Austin-1014 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 25th March 2020
Attendees:
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Eric Blake,
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=741
==
Reported By:steffen
Assigned To
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=779
==
Reported By:dwheeler
Assigned T
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=793
==
Reported By:steffen
Assigned To
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=802
==
Reported By:eblake
Assigned To:
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=840
==
Reported By:xroche
Assigned To:
The following issue has a resolution that has been APPLIED.
==
https://austingroupbugs.net/view.php?id=828
==
Reported By:nick
Assigned To:
echo n | sed '\n\nnd'
Above command returns 'n' with GNU sed, and nothing with BSD seds and
OmniOS sed. The standard says
-
In a context address, the construction "\cBREc", where *c* is any
character other than or , shall be identical to
"/BRE/". If the character designated by
The GNU version is more correct, in my opinion, in that the use of n as a
delimiter should take precedence over its use as control character alias with
the wording as is. The other versions appear to consider the BRE as
so does not match 'n'.
On Wednesday, March 25, 2020 Oğuz wrote:
echo
shwaresyst wrote:
> The GNU version is more correct, in my opinion, in that the use of n as a
> delimiter should take precedence over its use as control character alias with
> the wording as is. The other versions appear to consider the BRE as
> so does not match 'n'.
The Solaris sed behaves
On 25/03/2020 19:44, shwaresyst wrote:
The GNU version is more correct, in my opinion, in that the use of n as
a delimiter should take precedence over its use as control character
alias with the wording as is. The other versions appear to consider the
BRE as so does not match 'n'.
You have t
If it wasn't in single quotes, then that might be plausible, but I don't see it
as the intent since no other aliases are excluded as possibilities for after
the '/'. The initial "\n" makes 'n' the delimiter, the 2nd overrides it as
being the BRE terminator, and the following 'n' is the terminat
On 25/03/2020 21:09, shwaresyst wrote:
If it wasn't in single quotes, then that might be plausible, but I don't
see it as the intent since no other aliases are excluded as
possibilities for after the '/'. The initial "\n" makes 'n' the
delimiter, the 2nd overrides it as being the BRE terminator
On 25/03/2020 23:30, shwaresyst wrote:
yes, without them the argument would be "nnnd", after quote removal by
the shell. The reasoning in first reply was meant to show that the
non-GNU versions might be erroneously treating the second '\' as "do
contol alias processing always", ignoring that it
yes, without them the argument would be "nnnd", after quote removal by the
shell. The reasoning in first reply was meant to show that the non-GNU versions
might be erroneously treating the second '\' as "do contol alias processing
always", ignoring that its use as delimeter overrides that inter
yes, without them the argument would be "nnnd", after quote removal by the
shell. The reasoning in first reply was meant to show that the non-GNU versions
might be erroneously treating the second '\' as "do contol alias processing
always", ignoring that its use as delimeter overrides that inter
Date:Wed, 25 Mar 2020 21:09:38 + (UTC)
From:shwaresyst
Message-ID: <1031615939.2118006.1585170578...@mail.yahoo.com>
| If it wasn't in single quotes, then that might be plausible,
As has been said elsewhere, that's nonsense. The quotes are just
making clear wh
18 matches
Mail list logo