Christiaan Hofman wrote: > On Nov 18, 2011, at 6:58, FZiegler wrote: > >> 1) The line `set value of field "Bdsk-File-1" to ""' has no effect. It is >> meant to erase that field, but it seems it either doesn't or the field gets >> regenerated on every save. Is there a better way that would actually remove >> it? >> > > You should never access those fields. Those fields only exists in the saved > file, they don't exist in the program. You only have the linked files, so if > you want to remove them you should delete those.
I understood the above and removed this line from my script, but now I do in fact have to ask: is there a simple change I could make in BibDesk's source so that on saving a file it *doesn't* write these "Bdsk-File-*" fields? (or at least writes empty fields?) Reason: I've always had my .bib file mirrored between my desktop and laptop, using Unison. That worked fine under 1.3.12. But now say Unison copies the file, desktop-->laptop. The next time I open it on the laptop and save even once, all Bdsk-File-* fields change so the next Unison run reports the file as no longer in sync, even if *I* made no changes to it. Actual user-made changes get drowned in the noise of these alias changes. As I don't actually need these fields in the file (thanks to the applescript you helped me write), I'd rather just get rid of them, than return to 1.3.12. Unless you suggest yet another way of solving this problem? I have a hard time believing I'm the first person to hit it. Francois ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
