-
Notifications
You must be signed in to change notification settings - Fork 94
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
Strange underlining with TERM=xterm and emacs #51
Comments
What version of |
Thanks for the quick response! notebook 5.2.2. I also attached the full pip list. I couldn't find a version in xterm.js, but the md5 is: 83343775b76ff1f25429f6b63ed5da3a ./lib/python2.7/site-packages/notebook/static/components/xterm.js/dist/xterm.js |
So the version of xterm we bundled was 2.9.2 - you can see it here: https://github.com/jupyter/notebook/blob/5.2.2/bower.json#L27 That still appears to be the latest release, if you want to open an issue on xterm.js. I can't see a similar issue already there. It's possible that they'll tell you to come back here because terminado or Jupyter is setting something up wrong, but if that is the case, hopefully we can get a better idea what to fix. |
Created xtermjs/xterm.js#1147. Thanks. |
Versions: terminado 0.8.1 and jupyter 1.0.0.
In radiasoft/jupyter.radiasoft.org#15 you'll see a screenshot of the issue. The terminal goes into underline mode when emacs starts, and stays in underline mode after exit.
reset
does clear the mode so I suspect the term init string.The term init string itself seems right:
However,
TERM=xterm tput init
does not put the terminal in underline mode.You can clear the mode with the reset SGR:
Therefore, it does appear that terminado/xterm.js is going into underline mode.
emacs, ncurses, etc. are all a couple of years old (Fedora 21) so I don't suspect them.
A workaround is to set
TERM=ansi
, which seems to avoid the issue, because there's noinit
for ansi.The text was updated successfully, but these errors were encountered: