Mail Archives: opendos/1997/02/11/01:01:34
On Sun, 9 Feb 1997, Ian 'DrDebug' Day wrote:
> >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.
Granted. However, since there are a lot of FREE programs out
there *with* ANSI support built in, there is no need not to
upgrade. Besides, no-one is saying that ANSI.SYS should be
eliminated at all, just that it shouldn't be built into the OS.
Since less and less programs rely on ANSI.SYS for anything, it
makes little sense to build it into the OS and force it onto
everyone. I *DO* however think it would be cool as a compile
option! I think ALL DOS drivers should have the option of being
built in with a recompile.
Everyone will get what they want this way.
> >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.
I just tried creating one using SCRPUT and didn't get this
problem at all. I guess I'd have to see exactly what your prompt
does to implement (or try anyways) one in 4DOS.
> >> 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.
Ok, no harm intended, I'm just trying to be helpful.
> >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.
No, no, I just like to help people with things like this. It's
kind of like a challenge if you know what I mean. I'm not just
trying to prove a point, I have fun doing stuff like this.
> 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...
Send me a copy of your actual ANSI prompt and let me have a go at
it. Probably best to do this off the list though since it
doesn't have much to do with OpenDOS. I'm working on a 4DOS
version of a prompt that someone else posted. It works now but
there is a minor glitch in it so I need to fiddle a bit. Even if
something can't easily be done with 4DOS alone, a simple C
program in conjunction with 4DOS's exec would solve any problems
(and be lightening fast and remove the need for ANSI.SYS).
Just email me your prompt, and I'll give it a shot.
TTYL
Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris
Computer Consultant | My webpage has moved and my address has changed.
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
mailto:mharris AT blackwidow DOT saultc DOT on DOT ca
Want the DR-DOS source code? Visit Caldera's website: www.caldera.com
- Raw text -