mirror of
https://github.com/apple/pkl.git
synced 2026-01-11 22:30:54 +01:00
Weird repl output and interactions #235
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghyatzo on GitHub (Oct 31, 2024).
hello, I've been using the repl but the experience has been a bit rough around the edges.
I am on windows and perhaps that is why, since i know that window support is just coming together.
For example, when I use the repl from the PS there seems to be a struggle with new lines and command submissions:
copy pasting a multiline expression is impossible as it adds
:characters on every new line?while the pasted content was
There seems to be some jumbled up text in the error messages:
Is this an issue with PS?
@bioball commented on GitHub (Nov 1, 2024):
Hm, I can't reproduce this on my machine (running Windows 11 on Parallels).
The weird characters suggests that your terminal is interpreting Pkl output as some other charset. This post on stackoverflow might help you: https://stackoverflow.com/questions/57131654/using-utf-8-encoding-chcp-65001-in-command-prompt-windows-powershell-window
This might solve your issue with terminating prompts too?
@ghyatzo commented on GitHub (Nov 1, 2024):
PS is using the
us-asciiencoding:out of curiosity, what is the encoding on your parallels VM?
Forcing it to
UTF-8doesn't seem to work?What i noticed just now though, is this line
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)(it was there also before changing encoding) may this be it?EDIT: I've found out that I was using the built-in Windows PowerShell which apparently it is stuck at 5.1 and left there to die.
I've tried installing and using PowerShell7, which uses UTF-8 encoding OOB, but also there I have the same issue:
Btw, how do I enable debug logging?
@bioball commented on GitHub (Nov 1, 2024):
Here's what I see:
Try running the steps in the answer here: https://stackoverflow.com/a/57134096/2460186.
Mainly, flow where you check a checkbox in the settings panel, and then restart Windows.
@odenix commented on GitHub (Nov 1, 2024):
I've had console encoding issues with many Java programs on Windows.
The only solution that has universally worked for me was to enable "beta support for UTF-8" in Windows as shown here: https://github.com/oracle/graal/issues/8593#issuecomment-2009163353
@ghyatzo commented on GitHub (Nov 4, 2024):
Sorry, this was an issue on my work computer and had to wait the weekend to get back to it.
Turning systemwide UTF-8, fixed the mangled characters, and some end line issues.
But didn't make everything smooth:
also tab completion doesn't work.
@ghyatzo commented on GitHub (Nov 4, 2024):
I did some digging around.
It seems that the issue is with
jlineand missing either theJansiorJNAlibraries (on windows), quoting from thejlinereadme:I am very not handy with JAVA, is there a way to include manually those dependencies? Does it need a Java SDK installed?
@odenix commented on GitHub (Nov 4, 2024):
Unless you're using
jpkl, there is no way to fix this yourself. Probably best to wait until this bug has been fixed.