Hi!
4--2004 16:47 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA Hi! I suggest using isatty:
EA write(isatty(1) ? 1 : 2, format (YES/NO)? , 17);
EA The above example would show the confirm prompt on STDERR if STDOUT is
EA redirected to a non-tty.
There may be trouble with
Hi!
5--2004 12:03 [EMAIL PROTECTED] (Steffen Kaiser) wrote to
[EMAIL PROTECTED] [EMAIL PROTECTED]:
Matthias once wrote a long mail saying how other DOSes deal with this.
SK He writes that DR DOS issues ANSI escape sequences. Actually they are fine,
[...]
SK in
Hi Tom,
The only reliable way is to trap int10, write a character using int21 and
see if it gets trapped.
I've seen (N)ANSI.SYS implementations doing direct screen IO.
You're quite right about that so this is not good.
however: talking about CLS, why not
1'st) write ESC J (or
Hi Steffen,
But back to the question: HOW DOES FREECOM KNOW THAT THE CURRENT STANDARD
OUTPUT IS THE DEVICE DRIVEN BY THE BIOS? Is it save / useful to use BIOS
functions. Or how can FreeCOM ensure the human sitting on the other side
of the line is seeing the results.
The only reliable way is
On Thu, 5 Aug 2004, Bart Oldeman wrote:
Hello Bart,
But back to the question: HOW DOES FREECOM KNOW THAT THE CURRENT STANDARD
OUTPUT IS THE DEVICE DRIVEN BY THE BIOS? Is it save / useful to use BIOS
functions. Or how can FreeCOM ensure the human sitting on the other side
of the line is seeing the
On Thu, 5 Aug 2004, Steffen Kaiser wrote:
a) you cannot detect an ANSI driver across the line **), and
b) you do not know for sure what CTTY is in place, except the
shell itself has invoked it ***).
True. And now my opinion is that you can only assume that a VT100-style
terminal is in place
On Wed, 4 Aug 2004 16:47:42 +0200 (MEST), you wrote:
Hi Everybody,
write(isatty(1) ? 1 : 2, format (YES/NO)? , 17);
I remember many years ago there's a development tools ASYNC
PROFESSIONAL, anyone interested to build a similar free version?
Rgds,
Johnson.
