On Thu, Jan 1, 2009 at 1:35 PM, björn <[email protected]> wrote:
> 2008/12/31 Brian McKee <[email protected]>:
>> On Tue, Dec 30, 2008 at 1:53 PM, björn <[email protected]> wrote:
>>> I have no access to network shares so cannot confirm (or debug) this.
>>> Can anybody else confirm (or debug, if possible) this bug?
>> FWIW, any old samba or appletalk share has the same issue - so any
>> shared directory from whatever second computer you have lying around
>> should be able to reproduce it.
> Ok, can somebody give me step-by-step instructions on how to enable
> some kind of sharing on a Tiger machine and how I then connect to it
> and reproduce the bug?  That would help a lot.

Hi Bjorn

These instructions are a bit more complete than is really necessary,
but I wanted you to have same setup I do for consistency.

Assuming the machines are on the same LAN,

On the Tiger 'server' machine - go to System Preferences -> Sharing
and turn on the 'Personal File Sharing' tick box.

On the 'client' machine in Finder from the 'Go' menu choose Network
and you should see the 'server' listed there.  Click 'connect' and
enter the username/password from the 'server' machine.  That will
mount the remote share and put it in the Finder window side bar.

Now hit 'Shift-Cmd-G' and enter /Volumes as the path.  The file share
will be on that list.  Use Cmd-Option and drag the share to your
desktop to create an alias.

Unmount the network share by hitting the little eject in the sidebar
or dragging the share to the trash.
Prove it works by double clicking the alias to remount the volume.
Now unmount it again.

Try it in Textedit - start the program, hit Cmd-O and choose the
alias.  Wait about one second and it will mount the network share and
show you the contents.

Now try MacVim...


Hopefully that was clear enough - let me know.
Brian

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to