a command in PATH but can
not execute it ? Bash and some other shells continue to search for command in
other elements of PATH. Is this behavior required by POSIX ? I think it may
lead to some difficult to debug bugs if a shell silently ignores this condition.
--
--
Siteshwar Vashisht
so even if they were
> distinguished somehow, you wouldn't get that in bash's default mode.
>
> > jinx$ type -t break echo
> > builtin
> > builtin
> >
> > makes them look just the same.Are changes to bash in this area
> > possible?
>
> I suppose posix mode could display `spec-builtin', but that doesn't seem
> compelling enough to break backwards compatibility.
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
>
>
[1]
https://github.com/att/ast/blob/e770c77e9816e156c6df4a455e71b5f9fff79310/src/cmd/ksh93/RELEASE#L48
--
--
Siteshwar Vashisht
(home) Jörg Schilling D-13353
> Berlin
> joerg.schill...@fokus.fraunhofer.de (work) Blog:
> http://schily.blogspot.com/
> URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
>
--
--
Siteshwar Vashisht
- Original Message -
> From: "Joerg Schilling"
> To: svashi...@redhat.com
> Cc: k...@munnari.oz.au, "chet ramey" ,
> austin-group-l@opengroup.org
> Sent: Saturday, September 15, 2018 1:23:42 PM
> Subject: Re: Status of pipefail for standard
