#131 when "sos execute" fails

closed-invalid
None
5
2007-01-16
2007-01-16
r corak
No

On THE 3.3B1 as well as 3.2 on WinXP.
I have ENTER re-defined as ENTER.THE.
In ENTER.THE I have SOS EXECUTE.
When I enter at the command line the command CANCEL and CANCEL fails because some file has ALT non-zero, I see on the screen output as if I were tracing the REXX code in the ENTER.THE macro. Specifically

*-* "sos execute" / command line first */
+++ RC=1 +++
Hit any key to continue...

also happens for "command sos execute".
also happens for "command nomsg sos execute"
also happens for "nomsg sos execute"

I'd rather just see the error message "n file(s) remain with outstanding changes" and not experience this interference.

Discussion

  • Mark Hessling

    Mark Hessling - 2007-01-16

    Logged In: YES
    user_id=86185
    Originator: NO

    I assume you are using Regina as your Rexx interpreter? If so then add "Trace O" at the top of your macro. This will suppress the traceback.

     
  • Mark Hessling

    Mark Hessling - 2007-01-16
    • assigned_to: nobody --> rexx
    • status: open --> closed-invalid
     
  • r corak

    r corak - 2007-01-17

    Logged In: YES
    user_id=1587066
    Originator: YES

    cool

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks