![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 5 years ago
Closed 5 years ago
#4464 closed defect (fixed)
No error message given for bad files on start-up command line
| Reported by: | Tom Goddard | Owned by: | Tom Goddard |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Logging | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
If I start ChimeraX listing a non-existent file on the command-line it simply exits with no error message
$ "/Users/goddard/Desktop/ChimeraX April 1 2021.app/Contents/MacOS/ChimeraX" test.py
$
Also if the file exists but raise and IOError then it exits with no error message. I would like it to give an error message and traceback.
Note:
See TracTickets
for help on using tickets.
Fixed.
Starting ChimeraX in GUI mode it opens the command-line files after the GUI Log panel is started and apparently any errors go to that log panel and ChimeraX is immediately shut down. I made these errors instead go to the shell.