Earnie Boyd Sent on 05 Sep 2004 22:56:16 -0400:
> Suresh Govindachar wrote:
>> [After hiding vim by renaming key vim related
>> files, and verifying that which vim returned
>> nothing, the vim command still worked in msys.]
> Did you have a vim session open while you were renaming?
> If yes, then it is possible that your session did not
> complete the rename. Windows does not allow you to rename
> an open file. MSYS tries to be smart and copies the file
> and then watches for the close to delete the old file.
> The current MSYS session would think the file had been
> renamed and the which program would not have found it as
> the cache in MSYS would have reported it not found. If
> the synchronization failed for the rename then you are
> likely to still have it. Or you have a copy somewhere
> else and you needed to do ``hash -r'' to find it.
> Nothing tricky is trying to be done. If you close all
> sessions and start over you should not have this problem
> unless you find that ``which vim'' returns a value.
I kept digging and found my mistake: /etc/profile had
the line "alias vim=hide_vim" causing the vim command
(I seem to remember that on Solaris 2.3, the which
command detected aliased commands too.)