If fusebox.init.cfm includes a bad template, the exception is silently swallowed

[scorfield]

Carl Stehling says:

I discovered an odd situation in a FB5 app. I was getting a 'variable undefined' error message for an attributes.scope variable defined in fusebox.init.cfm.

The source of the problem was that my fusebox.init.cfm file contained a <cfinclude...> tag for a missing template.
It seems that nothing was set in fusebox.init.cfm after the bad <cfinclude> tag. The error message didn't point at the actual source of the problem.

Is there any coding practice or config setting that could insure that errors yield error messages which point more directly to the source of the problem?