-
Notifications
You must be signed in to change notification settings - Fork 45
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
find_orb messes up terminal colour map #26
Comments
Well, that's a new one on me. I do sometimes see odd things if Find_Orb crashes. Normally, the In what terminal are you running? I'm usually using xfce4-terminal, sometimes rxvt. I see an Ubuntu logo on the screen shots, but I'm not really familiar with Ubuntu. If you run |
Also, it occurs to me that I should ask : do the screen colors you see when Find_Orb is running resemble those shown here? |
Sorry, I got sidetracked and forgot to continue responding to this issue.
That appears to be accurate. I see no remnant of the find_orb interface, just remnants of the colour-scheme.
I'm using xterm-256color / gnome-terminal on Ubuntu 18.04, as well as xterm-256color on CentOS 7 (via SSH).
It does!
Yes, that's exactly what it looks like. Additional note: This happens both on my Ubuntu system where I run find_orb locally, and on a remote machine that I ssh into. When it happens on the remote machine, the weird colour-scheme persists even after I disconnect the ssh connection (it's not clear to me that that is necessarily surprising, but I thought I'd mention it). |
Hmmm... just tried it in gnome-terminal on Xubuntus 20.04 and 18.04. The latter did cause me to see a compilation error that I'll have to fix (failed to find wide-character ncurses automatically), but neither misbehaved in the manner you described. I also tried ssh-ing into a CentOS machine; that also worked correctly. In both cases, I was running a 'current' version of the source code... is that possibly an issue? It could be I had something messed up badly when this issue arose nine months ago and fixed it since then without noticing it. (Worth doing a 'git pull' and re-make/re-install anyway; various things have improved since then.) Maybe it's an ncurses version thing. When running Find_Orb on an object, try hitting '.' (dot/stop/period). You should get some debugging text such as
If TERM is set to xterm-256color, as you describe, things really shouldn't be all that exotic. But it's worth a check... will give this a bit more thought and see up with what I can come. |
SOFTWARE 9.1 ORDER ISSUES Hello! Thanks again! 2021 十二月 27 15:32:36 GMT+08:00 |
Running find_orb in a linux terminal seems to mess up the terminal's colour map, in a way that persists after find_orb is no longer in use, persisting until the terminal is closed (fortunately it does not persist when a new terminal is opened). This is somewhat annoying when working on a small laptop monitor, as I don't really have screen real-estate enough to have multiple terminals up, so it's easiest to use one terminal for everything, but once the terminal has been used for find_orb, it's very straining on the eyes to try to use the terminal for other tasks (like browsing files, editing observations/scripts/commands, etc).
Here are a before and after screenshot from a test directory showing the change of colours:
Before:
After:
Is there some way to fix this so that the original colours return when find_orb is exited? Perhaps rather than changing the colour scheme of the terminal, find_orb just uses specific colours? Alternatively, when it changes the colour scheme, it could save the old settings in a backup somewhere and set them back when find_orb is exited.
The text was updated successfully, but these errors were encountered: