Win ansi bug fix #26
Win ansi bug fix #26
Conversation
|
Thanks for your help on this @branneman - could you check this branch? |
|
I cloned the bugfix-win-ansi branch, and ran I think your fix does not solve the problem somehow. And I'm starting to wonder if it's actually possible from inside a node application. Since it's a terminal (or environment?) setting maybe it's not mutable from inside node. Here's how it looks with And here's how it looks with So it basically only works when I manually set my But a more interesting question: what is the default value of the |
|
I think the default value is 'dumb'. I had the same problem on OSX with users having the TERM set to xterm-color instead of xterm-256color |
|
Ah! You've got a shell file which kicks off the app.js - that's a good thing because adding Windows-specific code there maybe the option. But |
|
Idea: you could also replace the shell file with a node.js file, which spawns a new process, maybe like this: var spawn = require('child_process').spawn;
// Force platform-specific terminal
var env = {};
if (process.platform === 'darwin') {
env.TERM = 'xterm-256color';
} else if (process.platform === 'win32') {
env.TERM = 'windows-ansi';
}
spawn(process.execPath, ['app.js'], {
env: env,
stdio: [process.stdin, process.stdout, process.stderr]
}); |
This fixes part of #12