I have run into similar problems when I have files of the same name and similar content open. Usually this is because I want to copy from them, but inevitably I will forget to close them and in the flurry of making small incremental changes and testing, change the wrong file.
Since the fact is, had I been thinking in the first place I would have:
[*:2no4orvi]opened them read only[/*:m:2no4orvi]
[*:2no4orvi]closed them when done[/*:m:2no4orvi]
[*:2no4orvi]forgotten to do something else that would of prevented the error[/*:m:2no4orvi][/list:u:2no4orvi]
I work with projects a lot, and in each occasion the file with similar name that should not be changed is from somewhere outside the current project’s tree. A good solution for me is if files outside the current project had deferent tabs, or background color or something. Since background color comes from the color layout decided by the file extension, I can see how it would be hard to change the background (is the current one white, tint or one of the funky ones Reid uses ) as the change would depend on what color the background is supposed to be. So it seems a change to the tab (similar to files opened as read only) would be the most workable.
Would marking files outside the current project tree work for the other folks interested in this post, or are the files you want to mark inside your project tree?