id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,difficulty 416,Make stock errors more usable programmatically,Moritz Heidkamp,,"If I call {{{(with-input-from-file ""foo"" read)}}} with foo being a non-existant file, I get the following exception: {{{ condition: (exn i/o file) exn message: ""cannot open file - No such file or directory"" arguments: (""foo"") location: open-input-file i/o file }}} The actual cause of this file i/o error was that the file didn't exist, however, only the error message containts this information. It would be nice if there was an additional property (maybe a symbol) that would allow for better programmatic handling of this other than the message itself (which is likely to change in future versions). This probably applies to other errors in the core, as well. This is mainly a suggestion. Any comments or better ideas?",enhancement,closed,minor,4.9.0,core libraries,4.6.x,wontfix,,,