Gracefully handle symlinked files

[Colin Marquardt]

When I grep for, say, *.csv files, and some of these are symbolic links to other CSV files (that were found in the same grep run), then change something in all the matches, wgrep leaves those symlinks like "There are 40 unapplied changes. (90 changed)".
Could wgrep find out that those matches were "magically" changed already?