SublimeSBT
SublimeSBT copied to clipboard
Entering a command in windows does nothing (no echo, no newline, no output)
I'm guessing this is the same as https://github.com/wuub/SublimeREPL/issues/88. I'm on Windows 7 32-bit ST2.
Ok, I've confirmed this an issue also on ST3. :( Submitting commands via the menu doesn't work either. What's weird is pressing enter to interrupt continuous compiling/testing works.
I'll see what I can figure out. Something tells me this isn't going to be an easy fix. :)
Thanks!
Let me know if there is anything specific I can do to help test/debug. Thanks, Pat
On Tue, Apr 2, 2013 at 8:31 PM, Jason Arhart - [email protected] < github.pck.374cd93cd6.notifications#[email protected]> wrote:
Ok, I've confirmed this an issue also on ST3. :( Submitting commands via the menu doesn't work either. What's weird is pressing enter to interrupt continuous compiling/testing works.
I'll see what I can figure out. Something tells me this isn't going to be an easy fix. :)
Thanks!
— Reply to this email directly or view it on GitHubhttps://github.com/jarhart/SublimeSBT/issues/7#issuecomment-15814443 .
Getting the same problem here.
Eureka! I figured out the problem!
JLine on Windows messes up using STDIN. Fortunately, JLine has a handy system property to let itself be disabled, and sbt runners typically use the environment variable SBT_OPTS
for passing extra stuff, like flags to set system properties.
So, on Windows, SublimeSBT now adds SBT_OPTS
to the environment when running SBT, with -Djline.terminal=jline.UnsupportedTerminal
to disable JLine.
If you wrote your own batch file to run SBT instead of using the installer you'll have to make sure it includes the SBT_OPTS
environment variable in the command line.
Nice job! Thanks.
So it's still not working under latested Sublime Text + latest version of this plugin…
This is a broken again with the latest version of SBT because it uses a different version of JLine. Fixing it for SBT 0.13.x will probably break it again for SBT 0.12.x
As a user, I am interested in getting this bug fixed. Any suggestions?
Is there a workaround?