racket / racket/racket

DrRacket CS read-eval-print-loop: doesn't evaluate or print output, just expects more input

Open
#5,036 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
5.2k
Forks
698
Avg merge
18h 34m
Merged PRs (30d)
5

Description

What version of Racket are you using?

DrRacket, version 8.14.0.1 [cs].

What program did you run?

Definitions in DrRacket:

#lang racket

Interactions in DrRacket:

> (read-eval-print-loop)
> (+ 1 2)

Pressing Enter after the last ) close-paren.

What should have happened?

It should evaluate (+ 1 2) and print 3.

If you got an error message, please include it here.

It doesn't print any error message or any output, it just keeps expecting another line of input after pressing Enter.

When putting in an expression with side-effects, it does not evaluate those side-effects either.

Please include any other relevant details

It works in DrRacket BC, and it works on the command line with Racket CS. It's just broken in DrRacket CS.

Related bug report for debug-repl: https://github.com/AlexKnauth/debug/issues/25

Contributor guide

Open the contributing guide

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

Reproduce the issue in DrRacket CS using the read-eval-print-loop interaction shown in the report, then compare it with DrRacket BC and command-line Racket CS. The work is done when (+ 1 2) evaluates and prints 3, and expressions with side effects execute instead of waiting for more input.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.