dc8f3c944dbfd9bad55c3789d81f2e0e60e6f225
				
			
			
		
	I'm not sure if this is the "right" way to handle exceptions, but it does correctly print the error message AFTER shutting down curses for me.
				
					
					Add a try: block to catch exceptions that occur before the main loop and to call ui.mainException().
				
			
			OfflineIMAP Copyright (C) 2002 - 2006 John Goerzen <jgoerzen@complete.org> This software comes with ABSOLUTELY NO WARRANTY; see the file COPYING for details. This is free software, and you are welcome to distribute it under the conditions laid out in COPYING. http://software.complete.org/offlineimap/ Please see manual.txt; the information previously in README has been moved there.
Description
				
					Languages
				
				
								
								
									Python
								
								97.1%
							
						
							
								
								
									Shell
								
								2.3%
							
						
							
								
								
									Makefile
								
								0.4%
							
						
							
								
								
									Dockerfile
								
								0.2%