-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Debugger menu and configurable input prompt #1187
Conversation
I say "Aye!". |
Hmm, something's wrong with Travis. |
At least it got to the compiling stage. I've got a package where half the time I can't get travis to clone the repo. Did you try restarting the build? |
Yep, I restarted it. |
Ah ok. I was reading it on my phone yesterday, and it looked like the build was stopping at the compile stage. But I see now it's just a normal tests thing. I'll get to it. |
Ok. it's passing now. |
Hold on, don't merge yet. After playing around on my work PC I realise I don't like the way this looks. I'll have to fine tune it a bit more. |
Now that the debugger is a minor-mode, it makes little sense to quit it with C-g. Specially since the user can move around and mark stuff, and C-g is used to clear the mark.
Ok, it works nicer now I think. The current version doesn't immediately remove the overlays, instead it removes them when the next input request is received or after a fraction of a second (whichever comes first). In my system, this is enough to avoid the flicker. |
Debugger menu and configurable input prompt
👍 |
overlay
the default, so the echo-area will be less crowded. When the top of the function is not visible, the top of the window is used instead.What do you say?