A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1191 ====================================================================== Reported By: geoffclare Assigned To: ====================================================================== Project: 1003.1(2016)/Issue7+TC2 Issue ID: 1191 Category: Shell and Utilities Type: Omission Severity: Editorial Priority: normal Status: New Name: Geoff Clare Organization: The Open Group User Reference: Section: 2.2 Quoting Page Number: 2346 Line Number: 74697 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2018-04-13 14:33 UTC Last Modified: 2018-04-20 15:40 UTC ====================================================================== Summary: The list of special characters in 2.2 is missing '-' and '!' ======================================================================
---------------------------------------------------------------------- (0003983) stephane (reporter) - 2018-04-20 15:40 http://austingroupbugs.net/view.php?id=1191#c3983 ---------------------------------------------------------------------- Re: http://austingroupbugs.net/view.php?id=1191#c3981 Other extensions that clash with POSIX that come to mind: - extra keywords that can't be used as function names (POSIX reserves some of ksh's) - special variables. POSIX lists a few like SECONDS, but not others like TMOUT, LD_PRELOAD and can't possibly list them all. - zsh's %?foo that is not taken as a glob (won't expand to %xfoo (to allow kill %?job unquoted) - csh-style history expansion (!, ^), still enabled by bash when running as sh, though that's only for interactive shells - echo options (-e from Unix V8 1981, -E from bash 1992, combinations like -nn, -ne) supported by many shells, a problem because there's no "--" to end the options with echo (though zsh supports "-" as a (clashing) extension). Here I'd say POSIX should be amended to allow at least echo -[eEn]* (note the * instead of +) to be unspecified, at it's clearly a case where POSIX fails to describe the current reality (or even the reality from 25 years ago). - &> redirection operator (foo &> bar per POSIX is "foo & > bar [nocommand]") (unlikely to be a problem in practice). - echo **/* (zsh) - .* expansion not including . and .. (pdksh/zsh) (though it's actually the behaviour most people would like) Issue History Date Modified Username Field Change ====================================================================== 2018-04-13 14:33 geoffclare New Issue 2018-04-13 14:33 geoffclare Name => Geoff Clare 2018-04-13 14:33 geoffclare Organization => The Open Group 2018-04-13 14:33 geoffclare Section => 2.2 Quoting 2018-04-13 14:33 geoffclare Page Number => 2346 2018-04-13 14:33 geoffclare Line Number => 74697 2018-04-13 14:33 geoffclare Interp Status => --- 2018-04-13 14:44 geoffclare Note Added: 0003956 2018-04-19 05:54 shware_systems Note Added: 0003971 2018-04-19 05:55 shware_systems Note Edited: 0003971 2018-04-19 15:32 stephane Note Added: 0003973 2018-04-20 09:52 geoffclare Note Added: 0003975 2018-04-20 13:30 chet_ramey Note Added: 0003976 2018-04-20 13:39 stephane Note Added: 0003977 2018-04-20 13:52 chet_ramey Note Added: 0003978 2018-04-20 14:09 geoffclare Note Added: 0003979 2018-04-20 14:35 chet_ramey Note Added: 0003980 2018-04-20 14:56 geoffclare Note Added: 0003981 2018-04-20 15:06 stephane Note Edited: 0003977 2018-04-20 15:22 geoffclare Note Edited: 0003981 2018-04-20 15:25 chet_ramey Note Added: 0003982 2018-04-20 15:40 stephane Note Added: 0003983 ======================================================================
