2008-05-01 14:05:11 +0100, Clint Adams:
> On Thu, May 01, 2008 at 01:47:46PM +0100, Stephane Chazelas wrote:
> > So, first it's an XSI extension, so I guess posh is not required
> > to implement it, but as it does, I think it shouldn't read the
> > $ENV file when not interactive.
>
> Hmm, it's probably better to just drop that functionality altogether
> then.
Hi Clint,
Note that it's an XSI extension or "must be implemented if
the system supports the User Portability Utilities option".
So it's like for "command -v" which in my opinion posh should
implement (but I think we already discussed that).
Note that posh implements $PPID, $PS{1..4} which are also part
of that. But it's true that it doesn't implement aliases and job
control.
I don't really care about the "interactive" side of things
($ENV, $PSx, job control), but I tend to consider that for the
scripting side of things, the optional features should be
implemented. For instance, if you don't have command -v, there's
no other reliable way to find out whether a command exists or
not. So you have to have something (either "command -v" or
"type").
Best regards,
Stephane
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
