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

Misbehaviour when piping into the Ammonite REPL #397

milessabin opened this issue Jun 2, 2016 · 4 comments

Misbehaviour when piping into the Ammonite REPL #397

milessabin opened this issue Jun 2, 2016 · 4 comments


Copy link

@milessabin milessabin commented Jun 2, 2016

I noticed this when attempting,

# yolo ...
curl -s | bash

The REPL is downloaded and launched, however garbage appears on at the REPL prompt.

The following is a smaller reproduction,

haoyi-mbp:~ haoyi$ echo "println(1)" | ~/amm
Welcome to the Ammonite Repl 0.5.8
(Scala 2.11.8 Java 1.8.0_25)
haoyi-haoyi@ println(1)

haoyi-haoyi@ ����������������������������������...

See also #367.

Copy link

@lihaoyi lihaoyi commented Jun 2, 2016

#367 is different - that's about using Ammonite's internal shellout syntax and letting it pipe external programs into each other, while this one is Ammonite itself behaving properly when piped into.

Both should be fixed...

@lihaoyi lihaoyi added the bug label Jun 11, 2016
Copy link

@cosmo-kramer cosmo-kramer commented Sep 3, 2016

I will try to fix this bug.

Copy link

@blendmaster blendmaster commented Sep 23, 2016

I'm getting this same behavior when feeding STDIN programmatically. If it helps debugging, I captured the actual output through xxd, which shows this odd expanding pattern of efbf bfef mixed with some terminal escapes.

tkroman added a commit to tkroman/Ammonite that referenced this issue Sep 23, 2016
@lihaoyi lihaoyi closed this in 67a4081 Oct 4, 2016
Copy link

@lihaoyi lihaoyi commented Oct 6, 2016

This is fixed in the latest unstable version COMMIT-67a4081, thanks to @tkroman!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants