On 10 August 2013 15:36, Glenn Fowler <[email protected]> wrote: > > it still has not been explained why special fs treatment like this > goes into ksh and not src/lib/libast/something > is this really something *only* ksh will trip over > or is it a more general problem that should be handled in a more general way > > if any other ast command/library/user could trip up over the same rigmarole > then it belongs in a common place > > and it still hasn't be explained how these fs extensions ignore > fs semantics and paradigms that until this point have been working fine since > 1970 > > in particular, just how many commands in the wild need -@ args now? > is this an opportunity to do something like > /dev/rigmarole@.../... > and have it magically work for all ast commands/libs/plugins
Is the discussion now finished? I don't like to join the mayhem, but as a humble user I'd like to politely ask if could you please just *fix* cd -@ pathname for the next release? We use it in production scripts, mostly for tagging or adding parsed/precompiled versions of the original files, to speed BLAST (blastp, psi-blast, phi-blast) processing up. Ced -- Cedric Blancher <[email protected]> Institute Pasteur _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
