Weirdness using Pry as Ruby REPL about sublimerepl HOT 11 CLOSED

I will try to look at it when time allows.

from sublimerepl.

Thanks.

from sublimerepl.

I, too, would like to utilize Pry in sublimeREPL. Like LeakyBucket, I can only see output upon exiting the REPL session. Thanks wuub.

from sublimerepl.

Full Pry support might a bit difficult at first from what I can see. It's a
rather complex project.
If you could tell me which pry functions are most useful, we could
prioritize correctly.

FYI: I've got pry running nicely in SublimeREPL (much better than irb) so
this is not something that you will have to wait for very long.

On Wed, Oct 31, 2012 at 7:03 PM, AGS [email protected] wrote:

I, too, would like to utilize Pry in sublimeREPL. Like LeakyBucket, I can
only see output upon exiting the REPL session. Thanks wuub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53#issuecomment-9955371.

from sublimerepl.

Alpha testers welcome: https://github.com/wuub/SublimeREPL/tree/pry
My ruby fu is not so great, I'll accept any constructive criticism wrt config/Ruby/pry_repl.rb ;)

tested on Windows, booting linux and OSX as we speak

EDIT:
Depending on your ruby setup and GEM install path some additional configuration can be necessary. On OSX I was forced to put those in my SublimeREPL user config.:

{
    "default_extend_env": {
        "PATH": "/Users/[user]/bin:/Users/User/.rvm/rubies/ruby-1.9.3-p125/bin/:{PATH}",
        "GEM_PATH": "/Users/[user]/.rvm/gems/ruby-1.9.3-p125:/Users/[user]/.rvm/gems/ruby-1.9.3-p125@global"
    }
}

Edit2:
I'm contemplating switching to Pry completely. Question to any ruby gurus out there: is such dependency considered acceptable in ruby community, or will it be a show-stopper for some?

Edit3:
text_transfer [Ctrl+, f] & [Ctrl+, l] and so on is now working similarly to the python version. Some ugly encoding/decoding going on, but it seems to be pretty reliable.

Edit4:
Pry's edit command should work on all platforms now (calling st2 executable on windows and subl on OSX/Linux)

from sublimerepl.

I'm contemplating switching to Pry completely. Question to any ruby gurus out there: is such dependency considered acceptable in ruby community, or will it be a show-stopper for some?

Pry itself is an easy dependency, and I think switching to it would be street-credulous.

Too bad about the Readline issues.

from sublimerepl.

@rking thanks! :)

Too bad about the Readline issues.

It's not that bad. Using ordinary editor tab gives us pretty good line editing and SubREPL implements it's own history.

The only bit of missing functionality is tab-completion... and I plan to take care of that pretty soon.

from sublimerepl.

Just got in. Thanks soo much for your work. I'll start testing tonight. Excellent!

from sublimerepl.

I've been using SubREPL pry for a few days now. It seems much faster and smoother than the previous irb implementation. It handles things like forgetting to close the brackets or quotes much, much better than irb did. Further, when those kind of errors occurred, all the characters on the screen after that error would lose their proper coloring and be rendered in the string color - this is now fixed with pry. I have yet to find anything problematic. I would like to figure out how to use the OSX "cmd + left" to return to the pry prompt vs. having to use "ctl + a". All that said, I am really happy that you decided to go the pry route. Great work!!

from sublimerepl.

Further, when those kind of errors occurred, all the characters on the screen after that error would lose their proper coloring and be rendered in the string color - this is now fixed with pry.

Actually, this is me and not pry ;) Unbalanced backticks ` were so annoying that I now replace them with normal apostrophes before they even reach SubREPL. https://github.com/wuub/SublimeREPL/blob/pry/config/Ruby/pry_repl.rb#L15

. I would like to figure out how to use the OSX "cmd + left" to return to the pry prompt vs. having to use "ctl + a"

Switching between REPL and other views is getting on my nerves a bit lately too..

I am really happy that you decided to go the pry route. Great work!!

No problem. Once I decided to drop the "generic" way to do things and finally accepted that there is no other way than to do some per lang development a whole new set of possibilities opened up.

from sublimerepl.

Pry powers default Ruby REPL since v1.3.0

from sublimerepl.