You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run sbt new scala/scala-seed.g8 in MSYS2 / Git Bash / Cygwin
The new task will ask for the new project name
problem
Typing characters into the prompt, but they will not be displayed. Also backspace gets interpreted as a character (\177), not as a deletion. Pressing either creates a project with weird name:
expectation
Typed characters are displayed, and backspace/delete delete characters (and arrow keys move, etc)
notes
sbt version: 12.8
Tried with Git-Bash: Git-2.20.1-64-bit
and MSYS2: msys2-x86_64-20180531
The text was updated successfully, but these errors were encountered:
Although this may have been fixed in sbt for sbt new, supershell still interferes the same way for g8Scaffold when a scaffold has variable parameters. Maybe this should be filed as a new issue.
The scaffold case is perhaps even more frustrating, because you're often in the middle of long-running interactive sbt shell session when using g8Scaffold, unlike sbt new—starting another shell session with --supershell=false disrupts you mid-workflow.
(I've tried various forms of set Global/useSuperShell := false and set g8Scaffold/useSuperShell := false in an interactive session without success in actually disabling the super shell, maybe that's a separate issue for upstream sbt).
steps
Run
sbt new scala/scala-seed.g8
in MSYS2 / Git Bash / CygwinThe
new
task will ask for the new project nameproblem
Typing characters into the prompt, but they will not be displayed. Also backspace gets interpreted as a character (
\177
), not as a deletion. Pressing either creates a project with weird name:expectation
Typed characters are displayed, and backspace/delete delete characters (and arrow keys move, etc)
notes
sbt version: 12.8
Tried with Git-Bash:
Git-2.20.1-64-bit
and MSYS2:
msys2-x86_64-20180531
The text was updated successfully, but these errors were encountered: