On 13 nov, 11:31, Ben Schmidt <[EMAIL PROTECTED]> wrote:
> rds13 wrote:
> > Hy,
>
> > Trying to eject a drive I came around a possible problem with MacVim.
> > If you open two files one on drive A the other one on drive B and then
> > close tab which contains drive A and try to eject drive A OSX will
> > tell you that it can't.
> > If you close MacVim then you can eject drive A.
> > This behaviour leads me to think that MacVim is keeping opened handles
> > on drive A while to me it looks like it should not.
>
> > Anybody to confirm the problem ?
>
> > I'm using 7.2.22 MacVim version on 10.4.11
>
> I suspect Vim's working directory is still on drive A and that is
> causing the problem. What happens if you give :pwd? Try doing a :cd to
> change the directory to your home directory and see if you can then
> eject drive A. It's not a bug, just a subtlety that can easily be
> missed!
>
> If not, perhaps Vim still has something open on account of the buffer
> still in the list. Try :ls to see what the buffers are and then :bd the
> drive A buffer, or to be more drastic, :bw it. I don't think this is the
> problem, though; if it is, perhaps there is a bug in Vim.
>
> Let us know what you find out.
>
> Cheers,
>
> Ben.
You're right current working directory is set to directory of first
open file on drive A.
Thanks for your attention.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
