As a matter of fact when I was playing with the socket interface I was using
Windows; I don't recall now what the issue was (maybe redirected in/output?)
although you and I did discuss it at the time.
Another tool to keep in mind is a keyboard/mouse emulator such as AutoHotKey;
it's surprisingly powerful and flexible and can often come in handy for stuff
like this.
m
----- Original Message -----
From: Ken Pettit
To: Model 100 Discussion
Sent: Thursday, March 17, 2016 2:24 PM
Subject: Re: [M100] Virtual-T IDE Question
Actually telnet will work with Windows also, I was asking about OS because in
LInux, it may be possible to script the screen scrape using 'netcat' vs.
requiring an interactive command line session. But I think the telnet session
really wants an interactive session ... scripting may need a simpler interface
with a single command / response protocol over the socket interface.
Ken
On 3/17/16 11:20 AM, Mike Stein wrote:
That's why I suggested scraping the screen first, but if you're running
Linux then the Telnet option as Ken suggests would probably be easier (although
ISTR some limitations with it when I tried it years ago).
But I'm curious: why do you need the error messages in text form?
m
----- Original Message -----
From: Kurt McCullum
To: Model 100 Discussion
Sent: Thursday, March 17, 2016 2:05 PM
Subject: Re: [M100] Virtual-T IDE Question
Sure but that would only give me an image of the screen. I need the
actual text to work with.
Kurt
On Thursday, March 17, 2016 10:52 AM, Mike Stein <[email protected]>
wrote:
Can't you just PrtScr(een)?
----- Original Message -----
From: Kurt McCullum
To: Model 100 Discussion
Sent: Thursday, March 17, 2016 1:32 PM
Subject: Re: [M100] Virtual-T IDE Question
Ken,
Everything I need to copy is in the error window on the screen but I
can't copy it to the clipboard. Would that be easier than writing to a file?
Kurt
On Thursday, March 17, 2016 10:12 AM, Ken Pettit <[email protected]>
wrote:
No. It would be super simple to add though ... the assembler and
linker already output through a common "stdout" handler (VT_Ide::Stdout in the
ide.cpp file). Would be a simple matter adding a line of code to also print
any messages to a file. The most time consuming thing would be to add a GUI
checkbox to enable it, and maybe an edit field / browse button for the
filename, and even that isn't much.
Ken
On 3/17/16 9:53 AM, Kurt McCullum wrote:
Is there a way to export the assembler error messages to a file?
Kurt
