On 22/03/2008, Ben Schmidt <mail_ben_schmidt@...
> > Here's an easier solution:
> > In buf_write() (fileio.c), if the buffer being written is being edited
> > in an ODB session, then force 'backup_copy = TRUE' (irrespective of
> > what 'backupcopy' is set to). This way I don't have to muck around
> > with the 'backupcopy' option and non-ODB buffers will not be affected.
> > To me, this seems like a better solution in every respect...any objections?
> I'm hesitant, but it seems good to me, Björn. For an ODB session, you are only
> ever editing a temporary file, so breaking links shouldn't be ever desired/needed,
> and forcing backup_copy = TRUE should never break things, but just slow them down
> at worst. I reckon it's worth doing and then correcting it if problems are
> discovered down the line. Be sure to document it in the help, of course, so if it
> causes problems down the track people have a good chance to discover why!
Argh! After spending ~1 hour trying to get this to work I finally
realized that ForkLift doesn't even support the ODB protocol. It
simply downloads a remote file to a temp directory and monitors when
it has been changed and then uploads it again.
So, I can't do anything about this. If anybody wants to use ForkLift
they will have to set 'backupcopy=yes' manually. There really isn't
anything else that I can do (unless I force 'backupcopy=yes' for _all_
buffers in MacVim...obviously not the nicest thing to do.)
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php