sublime as your IPython editor

[jps]

http://pypi.python.org/pypi/processing/0.50 is another library that will handle RMI and proxies.

tbh though, I'm not sure how much of a win it is to be able to access the current View via IPython.

[SteveCooperOrg]

tbh though, I'm not sure how much of a win it is to be able to access the current View via IPython.

The best I can come up with ATM, if you could attach to a running instance of Sublime, is the idea that it could make it easier to develop tests for plugins; eg, I could write a test that did this (pseudocode)

# get a copy of a window in sublime
wnd = getSublimeInstance().window[0]

# create a new view
vw = wnd.newFile()
vw.insert(0, "My test string")

vw.runCommand("findNext test")
assert(len(vw.sel()) == 1, "should have selected one instance")
assert(vw.sel()[0] = "text", "should have selected the word 'text')

This could make it easier to develop tests for plugins.

Also, possibly, there is the idea that you may want to run an automated or unattended process which uses Sublime as a 'text server', and uses the sublime API as you might use, say the MS Word COM interface to build documents.

Lastly, the idea reminds me of emacs/slime for developing LISP. In this setup, you actually attach to a LISP server from within emacs, and push commands from there. If I understand correctly, it might be good to push commands from Sublime into IPython, rather than starting in IPython and moving into Sublime. So I could type

dir(os)

in sublime, select it, choose the 'send to IPython' command, and watch IPython tell me what's in `os`.

Just fiddling with idea. I may have entirely the wrong end of the stick.

[jps]

ps. Sublime is a bit strange about when it will open a new instance from the command line. If you launched it from the command line to begin with then your IPthon edits will be sent there otherwise it will create a new instance for the first edit and behave as expected afterwards.

Took a look at this: When it's checking to see if it's already running, Sublime Text will compare the path name it was run from, and pretend the other instance doesn't exist if it differs. This is mostly to make my life easier during development, but it was biting you here because the check is case sensitive. If you change your script to be "C:\Program Files" rather than "C:\program files", you'll be fine. This will be fixed in the next beta.

[Chicken Pie4 Tea]

The link given in the first post is dead