bbluemel/ColdFusion — comment on commit 2a4265d55f014290adf7e6b450e8e7fe04a69735
File:  line 0
By bbluemel:

Any instance of an included file not needing cfoutput would be very rare and using a terrible implementation, most likely using Evaluate. And there really is no need to attempt to reinvent what cfinclude does (wrap around it to extend it - yes, like what cfwheels does) but cfinclude quite rightly does not transfer the cfoutput status from the current file onto the one being included.

I don't think wrongly highlighting non-cfoutput hashtags is the solution for the rare case someone is using a framework that uses the cfm files in a non-standard way.