>> since I have been using the setup exclusively for a couple of weeks now.
Thank you very much. It's nice to know that someone actually finds this useful.
>> wuub, if you want the bug(s) posted to the Github repo, let me know and I can do that.
Nah. I sometimes report bugs myself to close them with a commit message for future reference. But this orphaned process problem is already known (https://github.com/wuub/SublimeREPL/issues/17
>> No tab-complete in the REPL (...) REPL acts like a text file, and is therefore not manipulated in the way you intuitively expect (emphasis mine)
There are two extreme approaches to embedding a generic
interpreter inside a text editor. One is through standard text editing mode somehow piped to/from the interpreter (SublimeREPL) other is terminal emulation (SublimePTY). Problem is, I'm not happy with either of those. SublimeREPL looses all the terminal/console functions, while PTY looses all the nice editing properties of the editor.
There is a much better (in terms of usability) middle ground, something I like to call "cooperative interpreter". Basically a standard REPL, but one that knows it's being run inside ST2 and provides a side channel communication for autocomplete, thread management (think runaway loop) and maybe some better text-transfer/debugging facilities (+- what most interpreter GUIs do but with better front-end/back-end separation) . Sounds tempting, but there is a catch. There is no generic way to do it, you need a separate cooperative interpreter for each language you wish to support this way. I would probably manage to code something for python in my spare time, but that's it, with my recent workload everything is progressing superslow either way.
To cut the long story short: I know this is an issue, I bump into it every day, I think I know how to fix this, the only problem is lack of resources
>> Closing an R REPL tab in ST2 sometimes does not close the RTerm.exe process,
There is an ongoing issue with killing some types of subprocess REPLs (mostly on Windows). For some (e.g. Clojure, Scala) I used an easy to implement "soft_quit" solution that sends a "graceful exit" string before trying to kill the process. I've got reports that it helps (a bit).
Next version of SublimeREPL will include a soft_quit config for R:
- Code: Select all
It may help if RTerm is still responding but decided to ignore SIGTERM for some reason.
>> This may just be a general SublimeREPL bug that I'm not familiar with, but I thought I'd point it out in any case.
a) this is a known problem, b) I was unable to recreate it with RTerm. Can you think of a use case leading to an orphaned RTerm?