-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Frozen(ish) - Can't Quit #860
Comments
When starting sc-im it will be in normal mode. None of the normal mode commands work in that moment? whats in your .config/sc-im/scimrc? |
.config/sc-im/scimrc => non-existent heh Bog standard install, no changes or configs. I should also note that sometimes when this happens there is also nothing drawn at all. So open a sheet and you just get an empty terminal. Kinda a coin toss if you will get blank/empty vs it shows you the fields but input doesn't work and you only get the ctrl C feedback. Might also be worth noting if I get a blank/empty term if I resize sometimes it will spring to life and draw the sheet, just still ignores input. Sorry if this seems like an incoherent trickle of details but I'm not sure what might tip you off to what's going on. I had also wondered if this was maybe an issue with my term at a given size but I've tried (and reproduced) in another term. The base size for my terms are 640x540. That said I tried with the debug flag and got no extra output when it happens. I've also noticed when I got it to happen this morning that once I killed sc-im my term is still taking inputs strangely. So it's crapping out characters from mouse wheel rolls or clicks. 64;41;24M64;41;24M64;41;24M0;32;28M0;38;28m resetting the term reitterates all the mouse input as command not found...it really makes things get nutty. |
I have exactly the same issue, and I think it might indeed come from the terminal. With It works fine with |
I also just noticed that on some spreadsheets, upon opening, the normal mode is active, but with |
It's been a while but I'm fairly sure I've tried on xterm, sakura and urxvt and had the behavior show up each time...eventually. I'll try st for a while though I'm not "spredsheeting" much lately. **Sidenote - glad it's not just me heh. |
I've not used sc-im much but so far running with st I've not had the noted issue. Could be luck, term size or a million other things but but so far so good. |
I think the issue comes from the |
My main term Sakura also sets xterm-256color. So why (if this is the issue) does sc-im hate xterm heh. My double click action opens .sc (scala) files with xterm and it's immediately jank. Terminator also sets TERM to xterm and sc-im again...jank. Launching with urxvt sets rxvt-unicode-256color and sc-im seems to work as expected. |
Looking at the Makefile, sc-im is compiled with 256 colour support by default. I wonder if you're trying to run it in a terminal emulator that doesn't support 256 colours and this is somehow causing a rendering issue. What is the output of running |
Sakura is 256 as is urxvt. |
I've noticed some times I will open sc-im and it is unresponsive to input. However if I ctrl-c it will give me a prompt for :q + enter to quit but since it's unresponsive all you can do is something like kill -9
pidof sc-im
.Running sc-im - version 0.8.3 on 6.6.9-arch1-1
The text was updated successfully, but these errors were encountered: