3 ms·
He had me at "code/history" division. I really don't like the way I must usually enter functions in the basic interpreter (line by line, can't go back... unless
by f_sav 17y ago
He had me at "code/history" division. I really don't like the way I must usually enter functions in the basic interpreter (line by line, can't go back... unless I missed something?).
To me that's an interesting cross between an IDE (with completions, snippets etc.) and an interpreter.
- algorias 17y agoYeah, that's great to have. If only there was a way to run the code without it being erased, so you can seamlessly work on a single piece and test it repeatedly.
- thezilch 17y agoYou may like to try out the following (vim solution): http://m5.posterous.com/slime-like-communication-from-vim-to-ipython http://m5.posterous.com/slime-like-communication-from-vim-to...
- gnaritas 17y agoThere is, in Smalltalk, we call it a workspace. This shell is basically a crippled workspace tied to a transcript. Getting closer and closer to Smalltalk.
- zephyrfalcon 17y agoI thought that this kind of smug remarks was reserved for Lisp weenies, but apparently not. ;-)
- abecedarius 17y agoI do that with http://github.com/darius/halp http://github.com/darius/halp in Emacs.
- nas 17y agopyrepl allows multi-line editing of history. It's pretty neat, IMHO.