I'll comment that the lack of a public issue tracker and source code
repository is a major hindrance to bug reporting and patch
development---did somebody already identify or patch a particular bug,
or was it otherwise already fixed in the upstream?---and makes it
difficult to gauge release-worthiness.
--
Nathan Weeks
IT Specialist
USDA-ARS Corn Insects and Crop Genetics Research Unit
Crop Genome Informatics Laboratory
Iowa State University
http://weeks.public.iastate.edu/
On Tue, Sep 22, 2015 at 11:00 AM,
Date: Mon, 21 Sep 2015 15:38:48 -0500
Subject: Re: [ast-users] ksh93v?
Content-Type: text/plain; charset=utf-8
I've been finding so many bugs in Version ABIJM 93v- 2014-12-24 that I
don't see how it can be deemed release-worthy.
We need more people in the community to download the beta, test it,
make bug reports and even provide patches. Feel free to join in.
I'm trying to get out reports and patches out myself, but it's one of
those things where, as I investigate one bug, I find more bugs.
You use find -print0? So, some of the path names you deal with contain
embedded newlines? Have you tried tw? It's really quite powerful.
Terrence Doyle
Post by Aaron Daviesany idea when ksh93v will ship? i'm eagerly awaiting read -d '', which is currently the only reason i have for writing anything in bash
(i have to deal with a lot of trees of arbitrarily-named files, so find -print0|while IFS= read -rd '' is essential to many of my ad-hoc scripts)