Feature request: don't cause /dev/null to reload BC4

[bcfan2013]

I use BC4 with git. The diff commands for new files use /dev/null as the left side (or the right side if the file's being deleted).

Often, BC4 will interpret /dev/null as having changed somehow, and asks me whether I want to reload the that side.

Is it possible to add an exception for things like /dev/null that will produce a null output? Or, if the output is truly empty, it shouldn't ask me whether it's changed or not. Thanks!

[Aaron]

Thanks. We'll look into adding dev/null support in the next update.