Even more fun:
,[ mksh ]
| __> msh
| __> type -p which
| which is /bin/which
| __> type which
| which is /bin/which
| __> command -v which
| /bin/which
`
,[ ksh ]
| __> ksh
| __> type -p which
| which is /bin/which
| __> type which
| which is a tracked alias for /bin/which
| __> comm
On Sat, May 03, 2008 at 09:52:16PM -0500, Manoj Srivastava wrote:
> On Thu, 1 May 2008 14:47:54 +0100, Clint Adams <[EMAIL PROTECTED]> said:
> > On Thu, May 01, 2008 at 02:33:04PM +0100, Stephane Chazelas wrote:
> >> I don't really care about the "interactive" side of things ($ENV,
> >> $PSx, job
On Thu, 1 May 2008 14:47:54 +0100, Clint Adams <[EMAIL PROTECTED]> said:
> On Thu, May 01, 2008 at 02:33:04PM +0100, Stephane Chazelas wrote:
>> 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
2008-05-01 14:47:54 +0100, Clint Adams:
> On Thu, May 01, 2008 at 02:33:04PM +0100, Stephane Chazelas wrote:
> > 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 b
On Thu, May 01, 2008 at 02:33:04PM +0100, Stephane Chazelas wrote:
> 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
5 matches
Mail list logo
