-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
DrRacket internal error, difficulty w/^C #601
Comments
Weird. The window persists despite my efforts to kill it through the OS. I can't find the process. Here are some additional error messages I was seeing at the terminal. Killing the terminal window from which I launched drracket didn't close the GUI immediately, but after I closed the terminal window, then tabbing back over to the GUI it finally disappeared.
|
Not the main point, but the <menukey>-1...<menukey>-9 shortcuts are
following what seems to be standard in browsers (and it actually is quite
handy to have a keystroke that means "go to the rightmost tab" I've found!)
Robby
|
Oh! Neat. Well, TIL! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not entirely sure I can describe how to reproduce this, but I wanted to report. The window pop-up reports a DrRacket internal error, and the terminal provides me the following:
I'm on my MacOS M1 machine running 8.7. I opened DrRacket from terminal, and ran a big-bang program. I believe it was running in the background. I then had the file open dialog open also. I tried from the terminal to ^C ^D drracket, but it didn't immediately close, and instead seemed to hang there. When I tabbed back over to drrracket, I believe that's when this window popped up. Sorry I don't have a clearer sequence to report, but I hope the stack trace is useful at least.
When I started up drracket, I did so passing a goodly number (~10) files with it. I only bring that up because I saw that when I do so, the file name keyboard shortcuts go 1: 2: 3: ... 8: , then followed by a bunch of no-name ones, and then the last one is labelled 9:. That seemed odd, so I mention it.
The text was updated successfully, but these errors were encountered: