Visual debugging in secondary files #56
Conversation
|
Proposed appearance of the GUI with debugger panels:
Appearance of breakpoints (red background) and the debugger stopping point (dark blue)--already implemented but not submitted:
|
| On the other hand, we shouldn't go out of our way to support multiple | ||
| simultaneous debug sessions--following a single debug session already requires | ||
| very close attention by the user. | ||
|
|
There was a problem hiding this comment.
Another detail: If two debug sessions stop in the same file, how do you highlight 2 stopping points? The stopping point highlight would need to change based on the which debugger tab is active.
|
As we discussed in the coq call, I think it would be better to only allow one debug session per process of coqide. This will simplify the design and avoid headache for the user. |
|
@Zimmi48 Perhaps you would merge this? |
|
@jfehrle is this up-to-date with the current implementation plans? If not, maybe you want to add a note on what changed. |
|
Yes, it's current. OTOH this CEP is meant to give some analysis, suggest alternative approaches and facilitate a discussion in order to get feedback on the ideas. It's now a historical artifact. It's not a spec, nor is it user or internal documentation, so updating it seems unnecessary. Nor do I consider it as constraining the implementation, either--if I come up with better ideas during the development process, I may adopt them and then (if necessary) defend those changes during the review process. The last part of the user documentation (#14381) reflects the discussion of the CEP. |
Looking for general feedback--is this a reasonable plan?
Rendered: https://github.com/jfehrle/ceps/blob/debugger_gui/text/056-debugger-gui.md