I understand the logic for moving from local-Url to Bdsk-File-N. However, by
moving away from pure plain text, it creates a barrier to using BibDesk created
.bib files with other programs. Bummer.
As an example, consider extracting a list of all attached PDFs. I can do this
with BibDesk's awesome Applescript support (and have done so). But that's a bit
slow of large files and means I can't combine extraction with processing in
another programmin language in a single file. Much faster would be using grep
or sed to extract just the Bdsk-File-N lines, but I don't know how to further
interpret the result.
So, I'd hoping someone can tell me how to convert the Bdsk-File-N string, e.g,
Bdsk-File-1 = {YnBsaXN0MDDUAQIDBAUGJ...AAAAAAAAAAAAALq}
into the path to the actual file. Ideally, there would be shell command,
pathfromalias "YnBsaXN0MDDUAQIDBAUGJ...AAAAAAAAAAAAALq"
If it exists, I've not found it. Nor have I found how else to do it. Since
BibDesk clearly does this, I'm hoping someone on the list can tell me how or at
least point me in the right direction.
I've seen solutions using osascript to access BibDesk's Applescript from the
terminal, but that leaves the problem of speed. I could use one of several
Applescripts to add the local-url information back to all the publications in
my .bib file, but that (a) adds more lines to an already WAY to big file and
(b) neuters the advantage of using aliases in the first place.
Thank you very much for any help.
Glenn
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
