ANSI escapes for input (Developers)
> > > I'm confused by this question.
> > Actually I was confused by your question!
>
> I am confused by your both. (joke)
>
> DOS it is about MICRO computers (like Commodore, Atari etc).
> ANSI-terminal it is from mainframe world.
ANSI terminals are not from the mainframe (which
doesn't really support them - although you can
quibble about that). But generally mainframes
only use block mode devices.
But regardless, ANSI/VT100 is what was standardized.
I have spent decades making the mainframe conform
to that standard (except I made it EBCDIC instead
of ASCII).
MSDOS 1.0 was probably written using a VT100
terminal connected to a PC, and I assume ANSI
has always been an option.
I don't see anything wrong with sticking with
what was standardized.
The Commodore Amiga and 68000-based Atari both
support ANSI X3.64 too. In actual fact - that
is what I have been interested in for nearly
40 years - what is preventing people from
switching from the IBM PC to the Amiga?
> Or in other words, try to do something, what is require different
> architecture for hardware and software. This is the same as making tea in a
> hat.
The standard is not so onerous that it can't
be implemented on a PC.
What do you suggest as an alternative anyway if
you want to write portable fullscreen character
applications?
Or are you saying it is impossible to make them
portable?
> I can say what you meet at end of this road. "dos does not support
> multitasking and multiusers". IMHO, does not have a sense repeat unix
> software (till solved this problems). Will be better keep and save exists
> micro-technology. It can be applicable for micro-controllers, drones etc
> (Real-time programs are a peak which is unattainable for modern software).
If you don't have a fullscreen application, you are
not affected regardless.
This is for people who want a fullscreen editor, like
microemacs, instead of a line mode editor like edlin.
BFN. Paul.
Complete thread:
- ANSI escapes for input - kerravon, 18.07.2023, 02:08 (Developers)
- ANSI escapes for input - mbbrutman, 24.07.2023, 03:01
- ANSI escapes for input - kerravon, 24.07.2023, 15:18
- ANSI escapes for input - DosWorld, 08.02.2024, 23:03
- ANSI escapes for input - kerravon, 09.02.2024, 13:17
- ANSI escapes for input - DosWorld, 08.02.2024, 23:03
- ANSI escapes for input - ecm, 24.07.2023, 17:01
- ANSI escapes for input - mbbrutman, 25.07.2023, 03:35
- ANSI escapes for input - kerravon, 25.07.2023, 12:34
- ANSI escapes for input - KormaX, 25.07.2023, 12:57
- ANSI escapes for input - kerravon, 27.07.2023, 07:15
- ANSI escapes for input - kerravon, 30.07.2023, 09:08
- ANSI escapes for input - kerravon, 31.07.2023, 15:21
- ANSI escapes for input - kerravon, 07.02.2024, 08:23
- ANSI escapes for input - bocke, 07.02.2024, 08:45
- ANSI escapes for input - kerravon, 09.02.2024, 10:00
- ANSI escapes for input - bocke, 09.02.2024, 20:10
- ANSI escapes for input - kerravon, 09.02.2024, 22:07
- ANSI escapes for input - bocke, 09.02.2024, 20:10
- ANSI escapes for input - kerravon, 09.02.2024, 10:00
- ANSI escapes for input - bocke, 07.02.2024, 08:45
- ANSI escapes for input - kerravon, 30.07.2023, 09:08
- ANSI escapes for input - kerravon, 27.07.2023, 07:15
- ANSI escapes for input - mbbrutman, 27.07.2023, 04:51
- ANSI escapes for input - kerravon, 27.07.2023, 07:25
- ANSI escapes for input - KormaX, 25.07.2023, 12:57
- ANSI escapes for input - kerravon, 25.07.2023, 12:34
- ANSI escapes for input - mbbrutman, 25.07.2023, 03:35
- ANSI escapes for input - kerravon, 24.07.2023, 15:18
- ANSI escapes for input - mbbrutman, 24.07.2023, 03:01