SublimeREPL
SublimeREPL copied to clipboard
evaluate in REPL not working for any language
I'm sure this is an issue with my system (sublime 3 pro, windows 10) thus it seems slightly inappropriate as an issue here, but in the interest of exhausting all possible venues for help:
I cannot get text in sublime text to be evaluated in the REPL. I suspect it is an issue with my configuration. I've tested R with R-box installed and Python and neither will evaluate selected text or files in the REPL. The REPL works great when content is copied over or typed, and R-box allows me to send commands to an Rgui.exe process but it would be so great to keep everything within sublime text
you can find a description of what I've tried here: http://stackoverflow.com/questions/35067863/initializing-r-box-to-send-code-to-repl
the same issue on win10 + sublime 3. in my case there even was no SublimeREPL package in "Install Package" list - I've installed it manually
Glad I installed it couples of weeks ago when SublimeREPL is still in "Install Package". The same issue here on Win10 + Sublime 3. Neither "Eval" nor "Transfer" actually works at this stage. Nothing happened when I click them, not even an error message.
Given the package is no longer available in Package Control, and the last commit was made more than a year ago (I had to fix the ipython repl myself, otherwise it's dead too), I would say this package probably has stopped updating.
It's a bit shame if this is the case considering it is this SublimeREPL that makes Sublime so powerful and unique.
Same problem here. I think this issue is identical to this one: https://github.com/wuub/SublimeREPL/issues/271
Giving my +1 to this, it is worth noting that it does work sometimes, but will sometimes start and stop working without me having taken any actions which I can identify as being a potential cause.
I am not sure if this is the same issue, but using sublimeREPL for R on windows 7, I found sometimes sublime would crash if a lot was printed to the sublimeREPL window. If this happens it would leave behind zombie Rterm.exe processes.
If you have more than one Rterm.exe running (for that or any other reason, maybe just closing sublime leaves them behind sometimes?) and you try to evaluate some code, it probably gets sent to the zombie rather than the new one associated with the window. The choice of which gets used may also be somewhat random... So next time it happens see if you have any extra of those processes running in the background.
So far I haven't bothered trying to make sure the process gets killed on close, but there is probably a way. I just make sure to kill all of them whenever I need to restart sublime.
Edit: I just saw JimAmuro's link above. That seems to be the right explanation and it looks like someone figured out a patch, but I haven't tried it.
I've had a lot of problems with this in windows and this is my current approach:
If the repl becomes non-responsive in any way (like ignoring evals and transfers) right click in the repl window in SublimeText and select "kill" to kill the current repl, then right click in the (now killed) repl and select "restart." Now it should be working again. In the event that it isn't: kill it again, shut down sublime and kill any unwanted processes such as python in the task manager if they are running. Start up sublime again and then boot up the repl. kill and restart if it still doesn't work.
So far this has solved my problem more or less every time with python repls. Once a repl becomes non-responsive, killing it and restarting it this way has been working consistently. Also, when I'm done working, I've gotten into the habit of killing the repl before closing SublimeText. Don't know if that helps, but it can't hurt.
@matthewjohnjamieson thank you, this workaround fixed the problem for me.
+1 for eval in repl / transfer in repl stopping working sometimes, with no error message. Killing and restarting repl works, but it would be nice not to have to do this every time I work in sublimetext.
Is there a fix for this problem? I tried methods mentioned above but very rarely it worked.
P/s: Found the solution over here. Worked like a charm.