|
Re: RFE: debugging in separate window: msg#00069lisp.clisp.general
Moin Joerg-Cyril Hoehle, > To have *DEBUG-IO* and *ERROR-OUTPUT* point to separate console windows (thus > keeping your standard console window clean from error messages) you can use: > (SETQ *ERROR-OUTPUT* > (SETQ *DEBUG-IO* > (OPEN "CON:0/0/500/300/CLISP-Debugger/AUTO/CLOSE" > :DIRECTION :IO))) > I don't know if people on UNIX/PC realize the power and usefulness of this. > I wish I could use this idiom on UNIX or MS-Windows too, not just the Amiga. The simplest way would be to open "/dev/tty" - this pseudo device is always pointing to the controling tty of a process. Unix/Linux/BSD supports pty/ttyp pairs to implement virtual lines for xterms and other toys. The idea behind that is, that one process can read/write into one side of the pair, and the other process would have the other side. This is used for xterm, at example. So clisp would just need to open a pty, and start minicom or cu on the other end of the ttyp pair. Bye Michael -- mailto:kraehe@xxxxxxxxxxx UNA:+.? 'CED+2+:::Linux:2.4.18'UNZ+1' http://www.xml-edifact.org/ CETERUM CENSEO WINDOWS ESSE DELENDAM ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RFE: debugging in separate window: 00069, Hoehle, Joerg-Cyril |
|---|---|
| Next by Date: | FFI:CAST segfault with gcc 3.2.2: 00069, Aurelio Bignoli |
| Previous by Thread: | RFE: debugging in separate windowi: 00069, Hoehle, Joerg-Cyril |
| Next by Thread: | Re: RFE: debugging in separate window: 00069, Sam Steingold |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |