Hello Jasen,

    On Friday November 29 2002 at 05:27,
    Jasen Betts [3:640/531.42] wrote to Gerald Miller,
    about:  Something unexpected....

 GM>>>> on errormsg (log /w
 GM>>>> %{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
 GM>> any error messages, short of sending the entire output to a
 GM>> file...
 GM>> ???

 JB> redirect stderr?

 somebat &>> errorfile

Yes, I had thought of that, but it seemed like a "using a big hammer"
approach.....  That's why the - "short of sending ...." :))

 JB> or don't use on error but use

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

Yes, yes, yes....  I'll give that a try.

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

No can do - no printer....  :((

 JB> 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)?

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

Now, I understand "adding different rules in the future..." idea.  ;-)>

I'll start looking...

           Thanks ... Gerald

... Comic book: the only place where men in tights are macho.

--- GoldED+/386 v1.1.5-21124