austin-group-l  

Messages by Thread

• Minutes of the 15th May 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Interpretation proposed: bug 1925 Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001925]: c17 -E output is incompatible with existing implementations Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001924]: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 8th May 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Interpretation proposed: bug 1915 Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001922]: testing report submission Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001922]: testing report submission Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001922]: testing report submission Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 1st May 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• bug report: New word splitting requirements inappropriate in locales with non-self-synchronising character encodings Stephane Chazelas via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001921]: A future C compilation interface needs to support "#embed" Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001921]: A future C compilation interface needs to support "#embed" Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Steffen Nurpmeso via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 24th April 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Issue 1920 Chet Ramey via austin-group-l at The Open Group
  • Re: Issue 1920 Stephane Chazelas via austin-group-l at The Open Group
  • Re: Issue 1920 Andrew Josey via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: (1920) splitting by bytes in UTF-8 Stephane Chazelas via austin-group-l at The Open Group
  • Re: [1003.1(2013)/Issue7+TC1 0001920]: read -d '' on invalid text without -r and IFS= Hans Åberg via austin-group-l at The Open Group
• [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2008)/Issue 7 0001919]: Add \A and \z to regular expressions (at least EREs) Austin Group Issue Tracker via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001918]: c16rtomb, c32rtomb Description Incorrectly References mbrtoc16() in Description Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001918]: c16rtomb, c32rtomb Description Incorrectly References mbrtoc16() in Description Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 10th April 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Formatting error for online issue 8 HTML docs, for make utility Wayne Pollock via austin-group-l at The Open Group
• Minutes of the 27th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Minutes of the 3rd April 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• the speed_t interfaces are inadequate (bug 1916) Andrew Josey via austin-group-l at The Open Group
• Call for input on 2.6.5 field splitting (bug 1915) Andrew Josey via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Chet Ramey via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Chet Ramey via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: Call for input on 2.6.5 field splitting (bug 1915) Geoff Clare via austin-group-l at The Open Group
• [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Online Pubs 0001917]: formatting error for uuencode historical algorithm code snippet Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 20th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001916]: termios: the speed_t interfaces are inadequate Austin Group Issue Tracker via austin-group-l at The Open Group
• Interpretation for a 30 day review (1857 revised) Andrew Josey via austin-group-l at The Open Group
  • Re: Interpretation for a 30 day review (1857 revised) Niu Danny via austin-group-l at The Open Group
  • Re: Interpretation for a 30 day review (1857 revised) Geoff Clare via austin-group-l at The Open Group
• [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Steffen Nurpmeso via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Geoff Clare via austin-group-l at The Open Group
  • Re: [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* stef...@sdaoden.eu via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2016/18)/Issue7+TC2 0001915]: clarification of 2.6.5 field splitting of 2.5.2 special parameter $* Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 13th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001914]: expr: short-circuit evaluation Austin Group Issue Tracker via austin-group-l at The Open Group
• mailing list archive seems to stumble over HTML like text Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: mailing list archive seems to stumble over HTML like text Lawrence Velázquez via austin-group-l at The Open Group
  • Re: mailing list archive seems to stumble over HTML like text [SECURITY] Christoph Anton Mitterer via austin-group-l at The Open Group
  • Re: mailing list archive seems to stumble over HTML like text [SECURITY] Andrew Josey via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Lawrence Velázquez via austin-group-l at The Open Group
  • Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Austin Group Issue Tracker via austin-group-l at The Open Group
  • Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Chet Ramey via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Harald van Dijk via austin-group-l at The Open Group
  • Re: Fwd: Re: [1003.1(2024)/Issue8 0001913]: clarify/define the meaning of n<&n and m>&m redirections Geoff Clare via austin-group-l at The Open Group
• [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
  • [1003.1(2024)/Issue8 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• [Online Pubs 0001912]: sysconf lacks variable for {CHARCLASS_NAME_MAX} Austin Group Issue Tracker via austin-group-l at The Open Group
• Minutes of the 6th March 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
• Fwd: [mikehaertel/minrx] Support new POSIX 2024 non-greedy repetition operators ?? *? and +?. (Issue #12) Niu Danny via austin-group-l at The Open Group
  • Re: Fwd: [mikehaertel/minrx] Support new POSIX 2024 non-greedy repetition operators ?? *? and +?. (Issue #12) Geoff Clare via austin-group-l at The Open Group
• Can we no longer edit our own notes on bug tracker? Niu Danny via austin-group-l at The Open Group
  • Re: Can we no longer edit our own notes on bug tracker? Geoff Clare via austin-group-l at The Open Group
  • Re: Can we no longer edit our own notes on bug tracker? Niu Danny via austin-group-l at The Open Group
• [1003.1(2013)/Issue7+TC1 0000793]: Regular Expressions: add REG_MINIMAL and a minimum repitition modifier Austin Group Issue Tracker via austin-group-l at The Open Group
• I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Steffen Nurpmeso via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Niu Danny via austin-group-l at The Open Group
  • Re: I still find the resolution Bug1857 not satisfactory. (topic: regex) Geoff Clare via austin-group-l at The Open Group
• Minutes of the 27th February 2025 Teleconference Andrew Josey via austin-group-l at The Open Group
  • Re: Minutes of the 27th February 2025 Teleconference - SIGFPE Fred J. Tydeman via austin-group-l at The Open Group
• [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro C via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Eric Blake via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn lanodan Monnier via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn lanodan Monnier via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Haelwenn Monnier via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Lawrence Velázquez via austin-group-l at The Open Group
  • Re: [Issue 8 drafts 0001616]: Standardize mktemp utility Alejandro Colomar via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group
  • [Issue 8 drafts 0001616]: Standardize mktemp utility Austin Group Issue Tracker via austin-group-l at The Open Group

• Earlier messages