Re: Are there two families of escapes sequences?

[Patrick]

On 14-10-27 08:38 PM, Paul Gilmartin wrote:
> On 10/27/14 13:28, legalize+jeeves wrote:
> > > The \E] part is (see ECMA-48) an OSC (operating system command).
> > Ah... my eyes kept misreading it as \E[, not \E].
> PMFJI, perhaps way late.  In my recollection, from trying to debug
> a terminal emulator, decades ago:
>
> o VT100 has two distinct modes:
>   - one used by shell commands.
>   - the other used by vi, etc.
>   Curses may not need to deal with the former.  And:
>
> o ESC sequences are time sensitive.  Vi uses ESC to exit text insertion
>   mode, distinguishing that use from ESC sequences generated by arrow
>   keys, etc. by the presence or absence of a pause after the ESC. I
>   can't imagine how this plays with the possibility that network packets
>   may by happenstance be split right after the ESC.
>
> -- gil
>
>
> _______________________________________________
> Bug-ncurses mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-ncurses


Thanks everyone :)

I had a terrible week, sorry for not participating properly in the 
thread I started.

I just want to mention that when I posted:

<ESC>]4;16;rgb:00/00/00<ESC>

<ESC> has just an ad-hoc way to represent the escape character

/E would have been much better. The output to file had this character as 
an unprintable square "mark" with a Unicode number inside it.

I also want to mention that it was false to say that the shell script 
gave correct colors, I was not comparing apples to apples as the shell 
script did not output 256 colors, I made a mistake.

Has anyone had success using 256 colors under fbterm? fbterm does not 
use the xterm escape sequences and does not seem to respect ncurses 256 
colors but it does respect mouse clicks while the Linux console does not 
appear to. Could anyone recommend another terminal emulator that will 
run without X ?

Thanks again-Patrick