Hi Gerald.

27-Nov-02 05:33:34, Gerald Miller wrote to Jasen Betts


 GM> Hello Jasen,

 GM> On Saturday November 23 2002 at 21:54, Jasen Betts [3:640/531.42]
 GM> wrote to Gerald Miller, about:  Something unexpected....

 GM>>> on errormsg (log /w %{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].ERR)

 GM>>> Maybe I'm not understanding the purpose of errormsg....  ???

 JB>> on errormsg executes the command after displaying the 4dos error
 JB>> message, on error executes it before the message. if there's an
 JB>> on error active i guess the error messages wouldn't print...

 GM> Seems kinda dumb.  I was hoping there would be some way to log any
 GM> error messages, short of sending the entire output to a file...
 GM> ???

redirect stderr?
  somebat &> errorfile

or don't use on error but use

on errormsg echo error at %_batchname:%_batchline >> error.log

or set up a printer capture and activate printer echo that way it'll come
on-screen and go into a file.

or just print less stuff on the screen.

 GM> Given that JPSoft no longer participates in this echo, I guess
 GM> this quirk will remain unaddressed.

 GM> My son (not a fidonet user) is using XBOOT3.BTM and he may have
 GM> discovered a glitch....  He put in a call to a batch that is only
 GM> to be executed once a year.  I'm thinking that there is gonna be
 GM> problems when there is a leap year involved in the calculations.
 GM> Opinion(s)?

yes.
that was the sort of thing i was thinking of when I mentioned the
posibility of adding different rules in the future...

 -=> Bye <=-

---