run SB+ process from TCL?

[slestak]

I apologize if this is elementary.  I do a lot of iterative testing, and always leave TCL before executing an SB process.  Is there a way to run a slash command from regular Unidata TCL?

One thought is to create a wrapper BASIC routine to call SB.EXECUTE, but if a general solution was available that would be great.  Almost like an SB.RUN or something.

[slestak]

Ok, answering my own question.  It appears the M voc items will take args, so "M FOO" will launch the SB process FOO.

This works pretty well, except the TERM setting is not obeyed.  Scrolled screen output (from a CRT stmt in a loop) is lost when the process ends.

[precisonline]

Is it safe to assume you've logged in to SB+ and then dropped to the colon before doing the M <cmd> thing?

If you want to capture the CRT output, you might use COMO ON <name> at the start and COMO OFF at the end to capture the screen output to a _PH_ item.  Much easier to deal with that way.

I'm not entirely following the "TERM setting is not obeyed"; if you were logged into SB+ and then dropped to the colon and then issued the M <cmd> from the colon, it should use the same terminal type as you originally set when you logged into SB+.  That's not happening?

And just so I'm clear, what's the point of dropping to the colon before issuing the SB+ process?  Is this to overcome that caching thing in Unidata?

[slestak]

I live in TCL pretty much.  I do not use the SB+ TCL either.  Just a '0' at the menu to drop to tcl.  Have to go there to compile my unibasic anyway.

I also have an 80x50 terminal, but SB does not respect the TERM setting.  I think I have a workaround.  My first attempt, running "M FOO" will leave you in SB when the process completes.  and it is the repaint of the SB screen which obscures my screen output.

I have also made a basic routine, SBR.TESTRIG that has a single CALL.SB.PROCESS("FOO") and it runs FOO and leaves me at TCL.

The reason I am doing this is pure laziness.  I am testing an extract and have run it 30-40 times this morning it seems.  It is a 3 step procedure to compile, M, slash command.  FIguring this out will allow me to use the command stack on a 2 step procedure.  .X2, .X2

Most automation is born out of laziness.

[precisonline]

I hear ya man... We stand in the presence of giants.

[slestak]

This is even better.

  1 * needed to call SB process from real TCL
  2 CALL SB.PROCESS(FIELD(@SENTENCE," ",2))


Then I can do SBR.TESTRIG FOO