Pyroom dies if file is unopenable

[Peter Frost]

Since the code was reorganised, PyRoom has started dying if you run "python pyroom.py blah.txt" and you don't have permission to open blah.txt. It used to print a friendly message to the buffer but now it just crashes and prints a traceback. It also fails to suppress the traceback if the "-v" option has not been used.

I'll look into this myself and see if I can fix it over the weekend.

[Adam Rooke (abelianr)]

Sorry for breaking that Pete! That was the one thing I didn't pay much attention to whilst re-organising the code. Cheers for looking into it.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Setting this as confirmed.

[Peter Frost (slimeypete)]

Status update: I've fixed the crash, and am currently working to implement the "verbose" option across the board. Whilst doing this I've had some thoughts about how errors should be reported, and have registered a blueprint to put buffer numbers outside the status line so that it can be used purely for reporting errors or giving the user extra information about what's happening. Any comments welcome! If everyone thinks it's a good idea then I'll implement it as a sort of "addendum" to this bugfix; if not I'll just register a branch with the fixes I've made.