pry/pry — Issue #469: pry -r file   - the file should be required inside the REPL
Author: banister
Created: 2012-02-10 11:18:57+00:00
State: open
Labels: feature

currently when loading a file into the repl using `pry -r file` any exception raise inside `file` will kill pry. If we moved the `require` into the repl itself then the exception could be caught and examined (using tools like `exception_explorer` or just `cat --ex`).

If people run their applications this way, instead of using the `ruby` executable then their entire application is backed by an interactive session which could enhance the running of their app by enabling them to drop into the REPL at any point. Unlike using `binding.pry` it is the same REPL session that backs their application rather than creating a new one with each `binding.pry` call, are tehre any advantages in this? what if we override `require` to force all code to pass through the REPL loop itself? then people could have pry commands interspersed throughout their code base