racket / racket/drracket

Automatically reload changed files option not working

Open
#506 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

https://user-images.githubusercontent.com/34615798/132786676-41412862-7452-48d3-85bd-981d2b5a89da.mp4

No matter which of the 3 options I pick in the "Automatically Reload Changed Files" option, it doesn't seem like racket auto reloads changed files from a different editor until you run the file, so I'm confused about this setting. I am also confused by "Revert" and "ignore as I'm not going back to an old file version, I'm wanting to go forward, so I suggest changing this to "Update" or "Reload".

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the issue in DrRacket using each of the three “Automatically Reload Changed Files” options and an external editor, then inspect the implementation of that setting and its “Revert” and ignore actions. Done means the selected behavior works as described and the action wording matches it.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.