Re: [Bibdesk-users] Bibdesk file paths and Google Drive

2023-02-08 Thread Christiaan Hofman
Good to hear! Perhaps for future reference, I noticed that one thing doesn’t work in the script, “remove” near the end should be replaced by “delete” (remove does not work when the value to remove is missing value). Christiaan > On 8 Feb 2023, at 19:54, Laurel MacKenzie wrote: > > I didn't

Re: [Bibdesk-users] Bibdesk file paths and Google Drive

2023-02-08 Thread Laurel MacKenzie
I didn't get a chance to try the script because the symlink method worked -- genius. Even after a restart, which ejected the fake GoogleDrive disk image, the file links now point to the right place. Thank you! On Wed, Feb 8, 2023 at 10:43 AM Christiaan Hofman wrote: > I thought of perhaps an

Re: [Bibdesk-users] Bibdesk file paths and Google Drive

2023-02-08 Thread Christiaan Hofman
I thought of perhaps an easier way to fix your problem using AppleScript.There is a trick to get the relative path in AppleScript even in the linked file is broken. Here is a script that you could use to fix the links. Run it from Script Editor. property oldPathPrefix :

Re: [Bibdesk-users] Bibdesk file paths and Google Drive

2023-02-08 Thread Nathan
The trick that Christiaan suggested is more relevant to this particular problem, but I thought I would mention that if one needs to convert the encoded bdsk-file path data to plain text (for example, if one is exporting to another app such as Zotero or JabRef), one can use the Python script

Re: [Bibdesk-users] Bibdesk file paths and Google Drive

2023-02-08 Thread Christiaan Hofman
No, the saved links are not in plain text, they are encoded data. Christiaan > On 8 Feb 2023, at 00:17, Andy Jacobson via Bibdesk-users > wrote: > > Can't you just edit the bib file and do a wholesale edit/replace of the path? > > Best, > > Andy > > On 2/7/23 16:09, Christiaan Hofman