Zsh Mailing List Archive
Messages sorted by:
POSIX (Was: PATCH: "sh" job control)
- X-seq: zsh-workers 8118
- From: mason@xxxxxxxxxxxxxxx (Geoff Wing)
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: POSIX (Was: PATCH: "sh" job control)
- Date: 1 Oct 1999 01:41:36 GMT
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- Organization: PrimeNet Computer Consultants
- References: <E11WhZy-00015a-00@xxxxxxxxxxxxxxxxxx> <19990930110741.B13153@xxxxxxxx>
- Reply-to: mason@xxxxxxxxxxxxxxx
Clint Adams <schizo@xxxxxxxxxx> typed:
:> I think CHECK_JOBS (with the opposite sense) would be a better name.
:I think that's reasonable.
:> Btw, you put SH_JOB_CONTROL out of alphabetical sequence.
:Ah, yes. I was mentally inserting spaces between the words.
:> What does POSIX say about it?
On the topic of POSIX:
% touch asdasd; chmod 755 asdasd
% ./asdasd ; echo $?
zsh: exec format error: ./asdasd
1 # <-- POSIX says 126
zsh: no such file or directory: ./foobar
1 # <-- POSIX says 127
:I don't know, but while we're on the subject, can anyone
:confirm or deny that bash's implementation of the 'command'
:builtin (command [-pVv] ...) is POSIX?
POSIX with (User Portability Utilities Option) says ``command [-pvV] ...''
-p: Use a default PATH that is guaranteed to find all standard utilities.
-v: Write string to stdout of pathname or command that will be used by the
shell, in the current shell execution environment....
-V: Write string to stdout that indicates how the name given in the
command_name operand will be interpreted by the shell, in the
current shell execution environment....
When the -v option is specified, standard output shall be formatted as:
"%s\n", <pathname or command>
When the -V option is specified, standard output shall be formatted as:
Geoff Wing : <gcw@xxxxxxxxx> Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@xxxxxxxx> Ego URL : http://pobox.com/~gcw/
Zsh Stuff : <gcw@xxxxxxx> Phone : (Australia) 0413 431 874
Messages sorted by: