-
Notifications
You must be signed in to change notification settings - Fork 25
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
I wish Ctrl+C worked #164
Comments
Oh wow... I use it daily and even though it sometimes requires a double tap, 50x should definitely kill the job... Can you give some context on what you were doing and what system you were on? (Eg was code being executed in the background, is this reproducible in your case etc) Also the version (Julia + package) please :) |
Hi! So I tried to reproduce yesterday's environment today in a new VSCode session, and (of course) it's started behaving itself now. I'm using VSCode on Mac, running Franklin in a terminal, editing various files in the editing area on the left. Using Julia 1.9.0 and Franklin v0.10.84. I'm guessing that VSCode just got tired eventually, and started playing up. If it starts again, I'll do some more investigation. Thanks! |
Thanks @cormullion , I did experience an issue with LiveServer that was not identical but maybe related to what you observed with Are you using the latest LiveServer too? ( I'll close this for now. (PS: catching interruptexception cleanly is probably worth a dedicated julia package at this point...) |
This is probably a VS-Code or Julia issue really, but LiveServer.jl doesn't like to quit (a commendable attitude in most other circumstances):
I know I can just kill the entire terminal, but I always worry that I might damage a file or something...
The text was updated successfully, but these errors were encountered: