| Joel Uckelman on Mon, 6 Dec 2004 12:45:52 -0600 (CST) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| [nimh-dev] TODO |
1. Make a TODO file.
2. Proposed augmentations for mhlib:
a. mhlib should read the environment variables described in mh-profile(5)
b. mhlib should handle sequences it does not yet handle
c. any others?
3. Decide what to do about mh-format: keep? toss?
If toss:
Maybe we want to define, e.g., a 'scanformatproc' key, which just
feeds the raw data to some program, which then hands its output back to
scan. That way, I could write my scan format in python or sed or perl or
cat it from /dev/random, and I could make it as (un)readable as I choose.
Maybe mhlib should understand mh-formats too?
_______________________________________________
nimh-dev mailing list
nimh-dev@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/nimh-dev