ipython/ipython — pull request #1008 by minrk (2011-11-17 21:42:54+00:00)
Title: don't use crash_handler by default

Now the excepthook shows a regular traceback, with a brief message about reporting bugs and how to enable to the big crash handler. Adding a `more/0` to interact inside `if more:`, I get:

```
In [1]: if 1:
Traceback (most recent call last):
File "/prefix/bin/ipython", line 9, in
load_entry_point('ipython==0.12.dev', 'console_scripts', 'ipython')()
File "/prefix/IPython/frontend/terminal/ipapp.py", line 393, in launch_new_instance
app.start()
File "/prefix/IPython/frontend/terminal/ipapp.py", line 367, in start
self.shell.mainloop()
File "/prefix/IPython/frontend/terminal/interactiveshell.py", line 220, in mainloop
self.interact(display_banner=display_banner)
File "/prefix/IPython/frontend/terminal/interactiveshell.py", line 288, in interact
more/0
ZeroDivisionError: integer division or modulo by zero

If you suspect this is an IPython bug, please report it at:
https://github.com/ipython/ipython/issues
or send an email to the mailing list at ipython-dev@scipy.org

You can enable a much more verbose crash handler with:
%config Application.verbose_crash=True
```

small fixes along the way:
* current Application added to configurables list, for use in `%config`.
* email addresses in full crash reports changed to ipython-dev, so they don't go straight to individual users.

Should close #695, and ameliorate #833 (doesn't fix the bug, but the message is more sensible)