Re: mailx: what if all implementations falsely implement a command?
Hello, as a P.S.: Steffen Nurpmeso wrote in <20191011222825.xo84w%stef...@sdaoden.eu>: |While slowly extending the test bed of "my mailx" i realized that |there exists no known implementation (Apple Mail, NetBSD Mail, |Tenth Edition Unix mailx, Illumos mailx) who implements |Reply/Respond the way the standard documents. |The standard says on page 2959, lines 98085 ff. | | Mail a reply message to the sender of each message in the | msglist. The subject line shall be formed by concatenating | Re: (unless it already begins with that string) and the | subject from the first message. If record is set to a filename, | the response shall be saved at the end of that file. | |Due to the way all checked [Mm]ailx?s do it the "first message" |constraint will never be satisfied. It seems to me that this The solution is a trivial five minutes fix. It requires adding a global bypass "struct message *firstmatch", to NULL that upon entry of getmsglist(), to set that if NULL in the function which mark()s, and then to use that bypass |strncpy(recfile, head.h_to, sizeof recfile); |mp = [msgvec[0] - 1]; instead of this ^ assignment in each function which uses that paradigm (Reply, for example). The(se) functions will be called only if there was a match, so the bypass will always be not NULL when we get there. ... Ciao, --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
Correction Re: Minutes of the 22nd October 2019 Teleconference (21st)
hi all Please note the dates of the meeting should be 21st October! regards Andrew > On 22 Oct 2019, at 16:41, Andrew Josey wrote: > > All > Enclosed are the minutes from yesterday’s meeting > regards > Andrew > > > Minutes of the 22nd October 2019 Teleconference Austin-978 Page 1 of 1 > Submitted by Andrew Josey, The Open Group. 22nd October 2019 Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Minutes of the 22nd October 2019 Teleconference
All Enclosed are the minutes from yesterday’s meeting regards Andrew Minutes of the 22nd October 2019 Teleconference Austin-978 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 22nd October 2019 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Joerg Schilling, FOKUS Fraunhofer Mark Ziegast, SHware Systems Dev. Apologies Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR * General news We briefly discussed gitlab usage. Andrew noted that the main development branches are protected. * Outstanding actions (Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 13th June 2019 and earlier) Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR list" OPEN http://austingroupbugs.net/view.php?id=1254 Action: Joerg to investigate how his shell behaves. Bug 700 - Nick to raise this issue with the C committee Bug 713 - Nick to raise with the C committee. Bug 739 - Nick to raise with the C committee. Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface, referencing bug note 4478. * Current Business Bug 1294: POSIX recognizes the existence of dynamically loadable, executable object files, but provides no way of producing them. OPEN http://austingroupbugs.net/view.php?id=1294 This was discussed at length on the call and will be continued next time. Notes are available in the etherpad. Next Steps -- The next calls are on: October 24 2019 (Thursday) This call will be for 90 minutes. October 28 2019 (Monday) This call will be for 60 minutes. Apologies in advance: Nick Stoughton, 2019-10-21, 2019-10-24 Eric Blake, 2019-10-28, 2019-10-31 Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. http://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/201x-mm-dd username=posix password=2115756# Andrew Josey VP, Standards & Certification, The Open Group Email: a.jo...@opengroup.org Apex Plaza,Forbury Road,Reading,Berks. RG1 1AX,UK. The Open Group Amsterdam 2019, Nov 4 - 7 http://www.opengroup.org/events ArchiMate, DirecNet, Making Standards Work, Open O logo, Open O and Check Certification logo, OpenPegasus, Platform 3.0, The Open Group, TOGAF, UNIX, UNIXWARE, and The Open Brand X logo are registered trademarks and Boundaryless Information Flow, Digital Practitioner Body of Knowledge, DPBoK, EMMM, FACE, the FACE logo, IT4IT, the IT4IT logo, O-DEF, O-HERA, O-PAS, Open FAIR, Open Platform 3.0, Open Process Automation, Open Subsurface Data Universe, Open Trusted Technology Provider, SOSA, Sensor Integration Simplified, and the SOSA logo are trademarks of The Open Group.
Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching
Harald van Dijk wrote, on 19 Oct 2019: > > On 23/09/2019 16:39, Austin Group Bug Tracker wrote: > >-- > > (0004564) geoffclare (manager) - 2019-09-23 15:39 > > http://austingroupbugs.net/view.php?id=1234#c4564 > >-- > >Interpretation response > > > >[...] > >If a pattern ends with an unescaped , the behavior is > >unspecified. > > Another problem here, one that already exists in the current wording: > > For patterns used for filename expansion, in current shells that treat > unescaped backslash as an escape character, behaviour is inconsistent when > unescaped backslash appears before a forward slash. > > Shells appear to typically implement 2.13.3 by effectively splitting strings > on forward slashes, then interpreting each component as a pattern if needed. > This results in some components ending with an unescaped backslash. > [...] > > However, 2.13.3 does not specify that strings are split on forward slashes, > so by the description in the standard, these patterns do not end in an > unescaped backslash. As such, I believe the current and proposed wording > requires treating the backslash as escaping the slash, which is not supposed > to have any effect. I believe the required behaviour is that indirect [a]\/b > and a\/[b] both find a file named 'b' in a directory named 'a'. > > Is my understanding correct? If so, should these patterns become unspecified > as well, to allow current and older shell behaviour? Good catch. Since there is no reason for a user or application to escape a slash with a backslash, I see no reason why this shouldn't be made unspecified. I suggest adding the following to the bug 1234 resolution: On page 2383 line 76261 section 2.13.3, append to item 1: If a character is found following an unescaped character, the behavior is unspecified. (this wording style matches the left-square-bracket case in the middle of the paragraph). -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
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=YEARLY;BYMONTH=3;BYDAY=2SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:EST DTSTART:20121104T02 RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT UID:5daeac0ae6...@opengroup.org DTSTAMP:20191022T071314Z ATTENDEE;ROLE=CHAIR:MAILTO:a.jo...@opengroup.org CREATED:20191022T00Z DESCRIPTION:Web/Project: Single UNIX Specification\nTitle: Austin Group tel econference +1 888 974 9888 PIN 618 156 403\nDate/Time: 28-Oct-2019 at 11: 00 America/New_York\nDuration: 1.00 hours\nURL: https://collaboration.open group.org/platform/single_unix_specification/events.php\n\n** All calls ar e anchored on US time **\n\nTopic: Austin Group teleconference\n-- -\nAudio conference informatio n\n---\n\nYou are invi ted to a Zoom meeting.\n\nMeeting ID: 618 156 403\n\nJoin from PC\, Mac\, iOS or Android: https://logitech.zoom.us/j/618156403\n \nor join by phone: \nUS: 888 974 9888\nUK: 800 031 5717\nDE: 800 724 3138\nFR: 805 082 588\n \nOther international numbers available here:\nhttps://zoom.us/u/adlvrb8IL j\n \nMeeting ID: 618 156 403\n\nor join from a H.323/SIP Device:\n Dial: 162.255.37.11 (US West) or 162.255.36.11 (US East)\nMeeting ID: 618 156 403\n\nShare from a PC or MAC: https://zoom.us/share/618156403\n \nOr iPhone one-tap (US Toll): +16699006833\,618156403# or +16465588656\, 618156403#\n\nAll Austin Group participants are most welcome to join the c all.\nThe call will last for 60 minutes.\n\n\nAn etherpad is usually up fo r a meeting\, with a URL using the date format as below:\n\nhttp://posix.r hansen.org/p/201x-mm-dd\nusername=posix password=2115756#\n\nBug reports a re available at:\nhttp://www.austingroupbugs.net\n DTSTART;TZID=America/New_York:20191028T11 DURATION:PT1H0M0S LAST-MODIFIED:20191022T031314Z ORGANIZER;CN=Single UNIX Specification:MAILTO:do-not-re...@opengroup.org SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Austin Group teleconference +1 888 974 9888 PIN 618 156 403 TRANSP:OPAQUE URL:https://collaboration.opengroup.org/platform/single_unix_specification/ events.php X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-VISIBILITY:40 X-JOINBEFORE:5 X-CATEGORY:Teleconference X-PLATO-SITE:Single UNIX Specification X-PLATO-SITEID:136 END:VEVENT END:VCALENDAR meeting.ics Description: application/ics
