From c291348d6adf15babf81ea41836754fd869c7996 Mon Sep 17 00:00:00 2001 From: Ethan Atkins Date: Thu, 17 Sep 2020 08:48:41 -0700 Subject: [PATCH] Use proxyInputStream instead of wrappedSystemIn I'm not sure why the scala.Console.withIn was using proxyInputStream while the other input streams were set to wrapedSystemIn. At any rate, using the wrappedSystemIn would likely prevent reading input from working with the thin client. --- .../src/main/scala/sbt/internal/util/Terminal.scala | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/util-logging/src/main/scala/sbt/internal/util/Terminal.scala b/internal/util-logging/src/main/scala/sbt/internal/util/Terminal.scala index f0c6a4651..d8ca471a3 100644 --- a/internal/util-logging/src/main/scala/sbt/internal/util/Terminal.scala +++ b/internal/util-logging/src/main/scala/sbt/internal/util/Terminal.scala @@ -518,8 +518,8 @@ object Terminal { } private[this] def withIn[T](f: => T): T = try { - inputStream.set(Terminal.wrappedSystemIn) - System.setIn(wrappedSystemIn) + inputStream.set(proxyInputStream) + System.setIn(proxyInputStream) scala.Console.withIn(proxyInputStream)(f) } finally System.setIn(originalIn)