Skip to content
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

Non Legacy REPL window becomes unusable #2487

Open
mintybayleaf opened this issue Apr 2, 2024 · 2 comments
Open

Non Legacy REPL window becomes unusable #2487

mintybayleaf opened this issue Apr 2, 2024 · 2 comments
Labels
bug Something isn't working output repl-window

Comments

@mintybayleaf
Copy link

When there is large enough input in the Calva output window when its the same as the input window it seems to render the REPL window unusable until you

  1. Disconnect the REPL
  2. Delete the REPL output.calva-repl file
  3. Reconnect

With these settings:

  "calva.redirectServerOutputToRepl": false,
  "calva.evaluationSendCodeToOutputWindow": true,
  "calva.legacyPrintBareReplWindowOutput": false,
   "calva.outputDestinations": {
    "evalResults": "repl-window",
    "evalOutput": "repl-window",
    "otherOutput": "repl-window"
  },

you can replicate like so in the REPL

(clojure.pprint/pprint (zipmap (map str (range 1 2000)) (map str (range 1 2000))))
@PEZ
Copy link
Collaborator

PEZ commented Apr 2, 2024

I could reproduce it, sort of, once. But before and after that it just prints the output as expected.

@PEZ
Copy link
Collaborator

PEZ commented Apr 2, 2024

Thinking it may not be a regression. But it probably is, so @mintybayleaf , if you can reproduce this more predictably than I can. Can you try a few times with legacyPrintBareReplWindowOutput enabled and disabled and confirm that it only happens with it disabled?

@PEZ PEZ added bug Something isn't working output repl-window labels Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working output repl-window
Projects
None yet
Development

No branches or pull requests

2 participants