Deleting a file in Eclipse does not trigger 'hg remove'

[dougxc@…]

Explicitly deleting a file in Eclipse where the file is currently being tracked by Mercurial does not cause the equivalent of 'hg remove' to be applied to the file.

[whit]

is this what CVS/Subclipse do? I decided against this because sometimes you need to remove files from Eclipse without it affecting your repository. For instance, if you deleted all your projects and re-imported them, would you want that to affect the repo?

[axel@…]

IMHO, it should be the other way around: Merclipse should automatically track what one does with standard Eclipse command (move, rename, delete, etc.). This is how the CVS plugin makes CVS bearable. If for any reason you want a local-only change, that should be performed via the "Team" menu or via the command line. Removing a project is a completely different kind of operation and does (as you said) not apply to these rules.

[whit]

I believe the problem here is that Eclipse doesn't necessarily differentiate between various actions that will cause a file to be deleted from Eclipse -- so telling whether or not the user pressed delete or is removing the entire project is non-trivial.

I'm not sure how important this should be, because if you delete a file it still shows up in the bottom box of the commit dialog, and you can always use Team->Remove to delete/remove it from the repo.

[axel@…]

I think removing projects does not process all files as being deleted.

My vote is in favor of an "hg remove" (it always did the right thing with CVS).