Message-ID: Date: Sun, 9 Feb 1997 07:07:27 +0000 To: opendos AT mail DOT tacoma DOT net From: "Ian 'DrDebug' Day" Subject: Re: [opendos] A more ordered fixlist In-Reply-To: MIME-Version: 1.0 Sender: owner-opendos AT mail DOT tacoma DOT net Precedence: bulk In article , mharris AT blackwidow DOT saultc DOT on DOT ca writes >I'm using Telix. I've used many text mode terminal programs. >I've yet to find one that needs ANSI.SYS. Yes, Telix supports >ANSI directly as well as several others. OK, but for each one that *you've* used that has automatic ANSI emulation, there are plenty of others that don't have it. >Nope. Use the %@exec[] command inside your prompt and it will >fit easily. That is what I used to do. You can then have it >call a batch file, or another command, alias, .exe, or whatever. > >It is much more powerful, and not at all difficult to set up. I >used to have quite a complicated "die-hard" prompt setup in 4DOS >in this manner. You might want to look up %@exec[] in the 4DOS >manual, also look up the PROMPT command for examples of how to >use %@exec[]. Yes yes yes, seen that, done than, read the book. I've been using 4DOS for 5 years or so, so I know what it can do. I also know that doing things this way adds extra CRLF sequences to your prompt after the exec has finished, which usually screws stuff up. >> Annoying for you, maybe. But for me, I display a whole bunch of info up >> in the top right of the screen (memory, date/time, session name etc.) >> This CANNOT be fast enough! ;-) > >It can if you use 4DOS's %_MEM, %_DATE, %_TIME variables and >countless other 4DOS variables and internal functions, along with >the direct screen write commands I mentioned earlier and the >%@exec[] function. Which is what I use. How do you think I get the info? As I said, I'm a 4DOS user too, you don't have to sell it to me. >If you're interested, send me your ANSI prompt in email, and I'll >write you up a 4DOS FAST version. Look. I know you're trying to be helpful, but it seems to me you're just padding out messages to prove a point. I've tried reducing the prompt size in the environment by using the exec function about a year ago, and as I said already it adds extra CRLF sequences in all the wrong places... -- DrDebug --------------------------------------------------------------------- Ian 'DrDebug' Day | Email: Ian AT darkblak DOT demon DOT co DOT uk Dark Black Software Ltd. | WWW: http://www.darkblak.demon.co.uk The Home of MrDebug | Dark Knight BBS & Fax: +44 (0)1480 471465 (THE Clipper debugger) | Tel: +44 (0)1480 403104 ---------------------------------------------------------------------