diff options
| author | Jeremie Courreges-Anglas <jca@cvs.openbsd.org> | 2018-01-08 13:39:07 +0000 |
|---|---|---|
| committer | Jeremie Courreges-Anglas <jca@cvs.openbsd.org> | 2018-01-08 13:39:07 +0000 |
| commit | d670e4bcf8842d82ede109e6e9ccc966a53cd56c (patch) | |
| tree | c4b6eb9e19682711ea17db2123fa984b078316c7 /bin | |
| parent | 4e5992164f99f33ff52a1f8ecc3e4c6321bb41d4 (diff) | |
Drop two outdated entries
Namely POSIX character classes and tilde expansion within parameter
substitution. While here, kill a useless line and fix a typo.
From Klemens Nanni
Diffstat (limited to 'bin')
| -rw-r--r-- | bin/ksh/NOTES | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/bin/ksh/NOTES b/bin/ksh/NOTES index 5fc1080bfbd..2e1d8254d84 100644 --- a/bin/ksh/NOTES +++ b/bin/ksh/NOTES @@ -1,4 +1,4 @@ -$OpenBSD: NOTES,v 1.14 2016/01/29 11:50:40 tb Exp $ +$OpenBSD: NOTES,v 1.15 2018/01/08 13:39:06 jca Exp $ General features of at&t ksh88 that are not (yet) in pdksh: - exported aliases and functions (not in ksh93). @@ -6,7 +6,6 @@ General features of at&t ksh88 that are not (yet) in pdksh: - signals/traps not cleared during functions. - trap DEBUG, local ERR and EXIT traps in functions. - ERRNO parameter. - - doesn't have posix file globbing (eg, [[:alpha:]], etc.). - use of an `agent' to execute unreadable/setuid/setgid shell scripts (don't ask). - read/select aren't hooked in to the command line editor @@ -34,7 +33,6 @@ Known bugs (see also BUG-REPORTS and PROJECTS files): an exit, but not sure. - `echo foo | read bar; echo $bar' prints foo in at&t ksh, nothing in pdksh (ie, the read is done in a separate process in pdksh). - Misc: Known problems not caused by ksh: - after stoping a job, emacs/vi is not re-entered. Hitting return @@ -249,15 +247,13 @@ POSIX sh questions (references are to POSIX 1003.2-1992) (eg, echo $(( ))). at&t ksh (and now pdksh) echo 0. Same question goes for `test "" -eq 0' - does this generate an error or, if not, what is the exit code? - - should tilde expansion occur after :'s in the word part of ${..=..}? - (me thinks it should) - if a signal is received during the execution of a built-in, does the builtin command exit or the whole shell? - is it legal to execute last command of pipeline in current execution environment (eg, can "echo foo | read bar" set bar?) - what action should be taken if there is an error doing a dup due - to system limits (eg, not enough feil destriptors): is this + to system limits (eg, not enough file destriptors): is this a "redirection error" (in which case a script will exit iff the error occured while executing a special built-in)? IMHO, shell should exit script. Couldn't find a blanket statement |