[Xastir-dev] TH-D7 start/stop files

[Curt Mills]

On Mon, 14 Jun 2004, Tom Russo wrote:

> I just noticed something about these new d7a start/stop files that were just
> committed.
>
> The "no-control-c" option seems correct to use before the TC commands, but
> I worry about haviung "##META <no-control-c>" before the very first command
> of a file as in the d7 files just committed --- isn't the point of the
> control-C to get the TNC out of CONV mode if we're still stuck there?  If so,
> then it could be asking for trouble not to send at least ONE line of stuff
> with control-c ahead of it in a start/stop file before launching into stuff
> without control-C's.

Send me a diff that works.  I don't own either of these rigs, so I
can't debug/test it myself.


> Which gets me to thinking --- why should xastir send control c at the beginning
> of every line of a start/stop file anyway?  Shouldn't it be enough to send
> just one, prior to sending anything else just to make sure the TNC is in CMD
> mode, and then send the rest of the file without it?  What am I missing?  Is
> there some TNC that needs a control C before every line of command input?
>
> If that makes sense, then command_file_to_tnc_port could put a single
> control-c into the output stream, and then just copy the lines.  The delays
> could still be inserted through meta commands in the start/stop files as needed.

Send me a diff.  I'll be happy to change it.  I think what you are
saying makes sense.  I believe the main thread is always the one
that controls what gets sent to the TNC.  You should be able to send
one ctrl-C and then do your business.

-- 
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"