-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node debugger issues with colour #76
Comments
For a quick and simple fix you can use the AnsiEsc plugin which converts escape codes in vim buffers to colored text regions. |
The AnsiEsc plugin certainly helps with the Terminal output, but not with the error messages |
FYI - Autocommand to fix the colors (also disable line wrap) in the vebugger terminal window. augroup MyVebuggerAugroupSetupTerminalWindow
autocmd!
autocmd FileType VebuggerTerminal :AnsiEsc
autocmd FileType VebuggerTerminal :setlocal nowrap
augroup END |
The integration with the node debugger seems to trip over the colour codes that node prints. These should probably be disabled using the
NODE_DISABLE_COLORS=1
environment variable.(EDIT: node doesn't seem to respect the variable on my system, so this might need to just be filtered out in the return strings instead)
To clarify, I'm seeing output like (after running
VBGevalWordUnderCursor
on the wordemail
):Vim's error output
Vebugger:ShellVebugger:Terminal
This happens for pretty much any command I run. The command itself seems to work, so I'm assuming it's the parsing of the output that triggers the error.
The text was updated successfully, but these errors were encountered: