John Mair banister

Organizations

@generalassembly @pry
banister commented on issue apeiros/ruby-community#19
@banister

contra +q helping new folk > the need to fight against spamming. If spamming is a significant problem (I don't even think it is in #ruby) then we j…

@banister
  • @banister 0ffc631
    Use Ruby 2.0 decorator syntax
banister commented on issue pry/pry#1275
@banister

@bcaplan thanks :) However if it's fixed on ruby 2+ then i'm pretty happy!

banister commented on issue pry/pry#1275
@banister

@rusterholz can you tell me a very simple repro for your issue? it sounds as if your problem occurs just in a normal pry session? If simply typing C-c

banister commented on issue pry/pry#1419
@banister

Sure but let me know the name first if possible ;) On Sat, May 9, 2015, 4:28 PM Yaniv Savir notifications@github.com wrote: Ahh, well, that would …

banister commented on issue pry/pry#1419
@banister

That would require putting a dependency of the binding of caller gem which is not only cross platform it's also temperamental and prone to occasion…

@banister

@deivid-rodriguez Sorry for not being clear :) Also, sorry for not responding earlier, i probably got distracted by some mundanity and forget to ge…

@banister

@deivid-rodriguez this auto-advance behaviour actually does break a bunch of plugins and causes weird/unexpected behaviour, i think it does affect …

@banister

Wish this was documented somewhere... not knowing about this rename drove me crazy

banister commented on issue pry/pry#1296
@banister

Looks like it could be a method_missing related bug :(

banister commented on issue pry/pry-stack_explorer#24
@banister

wow that's really weird, seems like a bug in rails' constant lookup code though?

banister commented on issue pry/pry#1403
@banister

I think the method is created on demand the first time the method is run, otherwise it delegates to method_missing. So try running the method first…

banister commented on issue pry/pry#1403
@banister

I can't replicate this, it works fine for me: [11] pry(#<DTest>):1> test2 another haha

banister commented on pull request pry/pry#1404
@banister

reverted via #1406 I'm against this as pwd is a likely variable/method name, and we want to avoid conflicts where possible, though i do appreciate …

banister pushed to master at pry/pry
@banister
banister merged pull request pry/pry#1406
@banister
Revert "Alias whereami to pwd"
1 commit with 0 additions and 1 deletion
banister opened pull request pry/pry#1406
@banister
Revert "Alias whereami to pwd"
1 commit with 0 additions and 1 deletion
@banister
banister opened pull request rweng/pry-rails#70
@banister
Enhance find-routes
1 commit with 12 additions and 7 deletions
banister commented on issue pry/pry#1396
@banister

@zw963 @deivid-rodriguez what if you just use a normal module here? and include the module into each of the commands? like so: module ByebugHelpers d…

banister commented on issue pry/pry#1396
@banister

I think you found a legit bug, thanks. However the recommended way of writing pry commands is to use so called 'class commands' now, see here: http…

banister commented on issue pry/pry#1374
@banister

@unixlife homie where r u these days ? how's life?

@banister

What happened to RUBY?!?! :(

banister commented on issue pry/pry#1383
@banister

It's too ambitious, but can we not delete it? Iirc it had some cool stuff that we might be able to cannibalize On Mar 4, 2015 4:02 PM, "Kyrylo Silin"