On Sep 19, 2009, at 11:19 AM, Andreas Fischlin wrote:
Yes I do have afp links present, but they do not matter. I just made a test. Moreover, note that the auto mounting happens not for the afp server that I reference in these afp URLs, it is the disk volume where my pdf repository resides on my main Mac and therefore I surmise it must be the file URLs that may continue to point to that volume or some other disk reference in the bib file? As Christiaan stated: relative path, fails after sync, file ids, point to the other disk and could cause the auto mount, absolute path do succeed.
Right, an afp: URL would be treated like any other remote URL; you should just end up with a generic icon. I was actually thinking of a file that resides on an afp/smb/nfs server, mounted under /Volumes and represented as a file: URL. In that case, the alias data may store server information; we don't know, though.
I have now also figured out what caused the automount. Having a Finder alias, not sym link in the pdf repository folder that gets synced, yet references a not synced pdf, since it resides outside the pdf repository folder, causes the automounting. So this is actually merely a problem of my particular bib file not properly constraining synced aliases only to originals that are not also synced. The only annoying thing is, if I happen to select a record with such a broken Finder alias, it is no longer possible to open the bib-file, since BibDesk gives not up trying to access the disk no longer available. I have to force quit BibDesk or mount the disk to open the bib file again (or edit away the selection as . Anyway your suggestions helped and made me understand the problem having nothing to do with BibDesk.
Can you take a sample when that happens? I'd like to see where it's hanging. Finder aliases are a different beast than what BibDesk uses internally, and they're a nuisance to deal with.
However, I would be glad if someone could tell me whether there is
a technique to extract from Bdsk-File-1{} entries that are broken in
such a manner the actual info, i.e. relative or absolute path. Since
my attempts to use AppleScript statements such as
set allLinkedFiles to (get POSIX path of linked files)
set allLinkedHFSFiles to (get linked files)
set allLinkedFileURLs to (get URL of linked files)
resulted in that situation only as a missing value item, yet the bib
file itself still contained the Bdsk-File-1{....} fields with lots
of for human eyes unreadable content.
Some time ago, I wrote a python program that extracts relative paths: http://homepage.mac.com/amaxwell/.cv/amaxwell/Sites/.Public/read_bdsk_file.py-zip.zip No guarantee that it keeps working, but you may find it useful.
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
