Yes I understand how to use Messages[symbol]
but that doesn't help much. I have no idea which important ones I may have missed in my search or even how many exist. Are there a mere 100 or so or tens of thousands? I am also aware of doing Messages[General]
which gives about 4 or 5 dozen. In most cases this should suffice however I would rather not repeat code native to the system by creating new Message
-s.
Since I have your attention how does one determine which messages go with Message
(for errors) and which go with Failed
and Failure
?
Error or Failed? I tend to use the following rules of thumb:
- Errors: tend to be bad argument inputs for example when a string is expected but string is defined with single quotes instead of double or expecting a list of text files but inadvertently sending a list of Excel files.
- Failed: Unable to retrieve anything from anywhere (files, data, other objects) or unable to perform a remote process anywhere in the world you may be connected to including your own darn computer drive.
Does this sound correct to you? How would you change it?
To sum it up I would like to see a list of most common Message
-s for both errors and Failure
(or Failed
) for use as a reference.
Thank you I hope I'm not asking for too much. :)
$Path
, automating the creation of packages, and lots and lots of custom interface construction, and automating many other general system tasks, but very little math and science although in a few months I will be flooded with it. so I guess I answered my own question. $\endgroup$FileNameJoin[{$InstallationDirectory, "SystemFiles", "Kernel", "TextResources", "English", "Messages.m"}]
. I don't know if the list is comprehensive. $\endgroup$