mhonarc-users

Re: Buglets/fixes (Was: Re: Changes summary for next release of mhonarc)

1996-01-25 18:47:13
1) There is a wrong RE that prevents mhonarc to start up:

      % bin/mhonarc
      /([\!\%\w\(_dot_)-\+=]+(_at_)[\w\(_dot_)-]+)/: invalid [] range in 
regexp at
      bin/mhonarc line 1871.
      %

   The fix was to move the minus to the start of the range:

   /([-\!\%\w\(_dot_)\+=]+(_at_)[-\w\(_dot_)]+)/

Yeah, I noticed it to.  That is what I get when I put in a quick
change and do not check it.  The key is to escape the '-' since
it can be used as a range operator:

        /([\!\%\w\(_dot_)\-+=]+(_at_)[\w\(_dot_)\-]+)/

2) Typo in mhonarc -help message

       -help                 : This mesage

I bet that's been there since the first release.

3) Get date part fills parse_date return list into wrong array:

        local($wday, $mday, $mon, $yr, $time, $hr, $min, $sec, $zone) =
                                       ^^^^^^
   because $time is not returned $hr gets out of range (timelocal.pl
   dies). $hr is filled with the seconds. Fix:

        local($wday, $mday, $mon, $yr, $hr, $min, $sec, $zone) =

Fixed.  Good catch.


4) -idxsize ignores negative numbers. 

   Nice to have feature: I would like if -<#> would
   display the first <#> of messages in an archive. But the
   final sulution would be a allow message range (alla mh?)

I'd like add range specification at sometime, but not for this
release.  For now, I'll modify mhonarc to just ignore the minus sign.

Thanks,

        --ewh