Possible node interfering with console color?
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- JavaScript
- Estrellas
- 122k
- Forks
- 37.3k
- Merge medio
- 4 d 2 h
- PR fusionados (30 d)
- 283
Descripción
There's a whole lot of things I don't understand here, so please let me apologize in advance for this ticket as a shambles.
Initially I was trying to work with a high quality console color library, and I was confounded because I had just switched to the modern Win10 console, with its 24 bit color support, and it wasn't 24 bit coloring. It's a big library by a big programmer, so I was surprised.
So I thought "it's just ansi codes, I'll do it myself," and tried to do it myself. Worked them out in console printf, looked good, node -e, and ... and ... wha?

The same string in the same console was working with printf and not with node -e console.log. The latter was getting downgraded to a different color range.
Okay, node must just not know it's 2-- wha?

So I tried using the FORCE_COLOR flag as a leader. No.

So I tried using it as an envvar. No.

So I switched to process.stdout. No.

And then I looked up my TERM setting. xterm-color-256. Initially I thought "aha!", except then I realized that's not the color you'd get from my testcase in a 6-cube.
Oh, dear. Am I in ... am I in 4-bit color in node, despite having a 24-bit terminal?
Wrote this to find out
const seq = n => new Array(n).fill(false).map( (_, i) => i );
const col = (r,g,b) => 16 + b + (g*6) + (r*36);
seq(6).map(b => {
seq(6).map(g => {
seq(6).map(r => process.stdout.write(`\x1b[38;5;${col(r,g,b)}m*`) );
process.stdout.write(' '); });
process.stdout.write('\n'); });
Yep.

Gulp.
Am I missing something? It seems like my terminal is set up for 24 bit, and node is manually downsampling my terminal output for me despite FORCE_COLOR. It couldn't be doing that, could it? That wouldn't make any sense.
What exists between node and the console which could be doing this?
So I thought I'd be tricky and see if some other language on the machine would get it right, yeah?
Tried python. ... lol

So then, yes, there is something between the language and the console, which is capable of screwing ansi codes up.
How do I find what that something is for node, so that I can find what's misconfigured in it, please?
Thanks
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Empieza reproduciendo el comportamiento con node -e console.log, process.stdout, FORCE_COLOR y el bucle de colores ANSI proporcionado en la consola moderna de Windows 10. Compara la salida de Node con printf y Python y determina después si Node cambia las secuencias ANSI o si lo hace una capa externa de la consola; se considera terminado cuando se hayan identificado el componente y la configuración responsables.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript, node.js
- Área
- cli
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 35/100