John Mair
It's because we use a simplistic approach to extracting the code, we read line by line looking for complete expressions. This works in 90% of cases as users don't typically...
There's a crazy gem called [sourcify](https://github.com/ngty/sourcify) which uses its own ragel scanner to do this accurately, you might get some mileague with that ;)
why aren't you just using `rake test` to run tests?
You're going to have a very hard time not using Rake, as almost every single ruby project uses it in one way or another ;) Anyway, `rake` is defined as...
Ah ok, no problem. Send me a pull request and i'll apply it ;) Thanks
It should be able to show the prompt source in this example, but it fails with an `EOFError` ``` ruby 90: NAV_PROMPT = [ 91: proc do |_, level, pry|...
Great detective work! Can you guys file a bug report with apple? It's the only way we can get stuff like this fixed: https://developer.apple.com/bug-reporting/ You can look here https://openradar.appspot.com/FB9658819 for...
It appears to be due to our syntax "correct indent" code, which irb doesn't have try typing this in pry before you paste `_pry_.config.correct_indent = false`
Hmm really? Try this then: `_pry_.config.auto_indent = false` and then pasting :)
@Kache this is due to the `.foo` shell functionality of pry, which automatically sends everything that starts with `.` to the shell Try this `Pry.commands.delete /\.(.*)/` And then try your...