> On Nov 12, 2015, at 07:45, macula <ir...@me.com> wrote: > > Allow me to respectfully contest this design decision. I can see the > advantages of the "new", alias-based system: links do not break when the file > is moved around within a given computer. But then again, they are changed > whenever the database is saved on another computer—hardly an uncommon usage > scenario in today's mobile, "cloud-y" world.
It’s shocking that when you save a file, all necessary information is updated? Your real objection here seems to stem from your notion that BibDesk is a text editor, and you think you know what bytes it’s changing. This is not really the case. > That said, Bdsk-File-N links generated on one computer are still valid, not > broken, on the other machine. No, they’re not, which is why they’re recreated; they’re partially correct, which means they’re partially broken. > In any case, I need to devise a solution as I cannot let my GitHub-hosted > bibliography grow at this explosive rate even after changing a single byte. What does this mean? Your bibliography file size is not growing at an explosive rate due to these changes. Do you spend a lot of time looking at diffs of it? Is Git really inefficient at storage? Adam ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
