Saving a file with the console focused saves the contents of the console
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
I experienced a bit of a calamity a few days ago. I had been working on a file in DrRacket for a while which I presumably didn't know I had already saved. I went and saved the file using the keyboard shortcut while my cursor was in the REPL console which prompted a Save As... window, in which I unknowingly overwrote my current progress with the contents of the console.
Is this intended behaviour? Why might someone want to save the text contents of the console? I know not to do this again but it seems like a horrible thing to learn by accident, especially since I can't seem to find any reason why someone would need to do this.
OS: Debian Buster x86-64
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the keyboard shortcut with the REPL console focused in DrRacket, then trace the save command from that entry point and inspect any existing save-related tests. Done means the intended console-save behavior is established and accidental overwriting of a file is prevented or covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100