I would like to emphasize that macula is not alone in these thoughts. > On Nov 12, 2015, at 8:44 AM, Maxwell, Adam R <adam.maxw...@pnnl.gov> wrote: > > 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.
Yes: I also have this notion/desire. For me, a main point of a bibtex database is that it is a text file that can be read by humans, and the Bdsk fields really go against this idea. >> 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? I do spend a lot of time looking at diffs of my database. Often I have collaborators who add or edit papers, and need to merge their changes. The autofilling of papers is fantastic, but the lack of portability, and the noise in the diffs is really a huge wart for users like macula and me. I believe that a simple option in the preferences for autofilling papers in a relocatable directory structure would satisfy many users needs. Bibdesk is generally a fantastic piece of software, so I usually just live with this issue, but it bothers me weekly. Michael. ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
