Re: [Bibdesk-users] Problems with bibdesk "auto-correct" file locations

[Christiaan H. <cmh...@gm...>]

On Dec 7, 2012, at 17:57, Adam Ginsburg wrote:

> I'm having a problem with bibdesk's file locations.  I'm using dropbox
> to sync my bibdesk.bib file, and another syncing software to sync the
> papers themselves (as they're too big for dropbox).
> 
> The problem: I've recently had to move my ~/Documents folder to
> another HD and replace it with a symbolic link.  This has apparently
> cause bibdesk to automatically switch to the full path to these files
> on the other HD (at least as far as I can tell; I can't get the
> "trivial python script" here:
> http://bibdesk-users.661331.n2.nabble.com/Loss-of-local-file-links-td2209604.html
> to work because of failed dependencies).  Since one of my machines
> doesn't have the full path bibdesk is looking for, I get a bunch of
> red paper clips = lost files if I save my .bib file on the machine
> with the symbolic link; saving from the other machine is fine.
> 
> Is there any way around this?
> 
> Thanks,
> --
> Adam

It will always have a relative path. But the relative path may not be what you think it is, because the symlink will be expanded, so the relative path it saves is the one *after* expansion. And that will only work on the machine with the symlink. The same is probably true for the full path (i.e. the alias.) This setup, using symlinks somewhere in the relative path, is not stable, so you should not use it. In general when you sync between different computers you should always have the relative paths (without symlinks) the same on both sides, otherwise it will almost certainly not work.Best is to have both the .bib file and the linked files in a single common root.

Christiaan