Comment 2 for bug 1015094

Apparently events are getting queued up in the background during the save process and firing upon the file watcher becoming re-enabled. There are a few ways to handle this, such as:
- Still emit signal from internFileChanged, but throw away when we reach mainWindow's fileChanged function.
- Remove the path being watched upon the file watcher becoming disabled and vice versa.
- Disconnect event/signal handles until saving is completed entirely.

I'm not 100% sure which one we would prefer here, but it is likely that disconnecting the signal all together might be the best approach, but I've been wrong before.

The other two options are just as effective, in either case.