Alex Roberts

Thank you. I have looked there now and have attempted to use what I think is the right key. I wrote: defaults write -app BibDesk BDSKAdditionalFieldsToCompleteKey '{ "Notetoself"; }' It does not give an error message but it does not seem to change anything either. Am I doing something wrong? Thank you for your patience with my lack of knowledge about this.

Thank you for releasing 1.9.4! It is great to have the preview pane back. I saw in the release notes that you added a new hidden preference for enabling autocompletion of fields for all fields, but I wasn't able to find it in the documentation. Might I please ask how I can turn on that hidden preference?

It would be wonderful to have autocompletion in the Series back. After more reflection, I realized that it is important to me to have autocompletion even in fields like Title that might seem less useful for a very specific reason: it alerts me to when I am duplicating an entry that already exists before I waste my time populating too many fields. That is, I might start typing a new bibentry's title and then realize, because of autocompletion, that I must already have an entry with that same title....

Sorry, I hadn't managed to find the preview issue among the tickets. Thank you for pointing that out. About the completion, I have always found it extremely useful to have completion in all the fields. I first noticed its lack in the Series field. Is there an option to turn it back on for all fields that were previously covered? (Even better would be a preferences pane -- or hidden preferences -- where one could turn it on and off for each field one by one, but I imagine that would be a feature ...

For the preview, I am using a custom HTML preview.

Autocompletion and preview stopped working in latest update Version 1.9.3 (6113)

Also, since you have marked this feature request as a duplicate, let me emphasize that the only feature I am looking for is the first part of the one mentioned in that related feature request. I think it would suffice to have a standard order of databases that BibDesk checks, e.g., it always checks LOC first before moving on to other options -- rather than having some complicated interface for choosing which version to use.

Yes, I suspected it was probably not useful -- except as an example of what I would like BibDesk to be able to do. Do other sites (like the Library of Congress) make a public API available? It would be great to see this feature become part of BibDesk in the future.