Re: [Bibdesk-users] Autofiling question
On Jan 7, 2013, at 7:32 AM, Christiaan Hofman wrote: > > On Jan 7, 2013, at 3:28, Dr. Adam M. Goldstein PhD MSLIS wrote: > >> On Dec 11, 2012, at 5:17 AM, Christiaan Hofman wrote: >> >> >> I followed the steps above, or at least, tried my best. It didn't work. The >> papers remained linked to the directory called Papers-1 wherever I moved it. > > In the above I assumed they were linked in the (old) Papers. Not some other > place like Papers-1. If they link there, they won't be relinked to some old > location, and there's no way to tell them to. So you need to move the folder > where they are linked to back to the (old) location first. Or you start the > whole thing from Papers-1. > >> This, even after I deleted the preferences file, selected and re-selected >> Papers. > > Preferences, again, are completely irrelevant for this. that is *only* for > auto-filing (looking up is not filing). > >> I created a disk image and put the Papers-1 directory on it, and then >> ejected it, so it could no longer be found. Now none of the PDF's will link >> to any folder, including Papers-1, no matter where I move it. >> > > Putting papers on an external volume is dangerous. You cannot just move them > there from outside BibDesk, because then BibDesk will loose them. This is > because the files won't be moved, but rather they're copied (you can't move > between disks, only copy). And then both the file identity and the (absolute > and relative) path changes, which means all links are severed. The only way > you can do this is if you move *both* the files and the .bib file at the same > time (with BibDesk not opening the .bib file), so that the relative paths > remain the same. > > It is not completely clear where your setup stands at this point. I hope you > have a backup (that works), otherwise you may not be able to get the links > back. > > HTH Unfortunately, I think I have mangled things so badly that I am going to have to reattach all the files by hand. I will take a look at the Applescripting possibilities. The PDF's are named using the cite keys as a basis, so it will be pretty easy to connect the PDF with the record. I suppose I couldn't just leave well enough alone! -- Adam M. Goldstein PhD, MSLIS -- z_california...@shiftingbalance.org http://www.shiftingbalance.org http://www.twitter.com/z_californianus -- http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=180621 -- Associate Editor Reviews Editor Evolution: Education & Outreach http://www.springer.com/life+sci/journal/12052 http://www.twitter.com/EEOblogger -- Spellman 205 (914) 637-2717 (msg) -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 http://www.iona.edu/faculty/agoldstein -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling question
On Jan 7, 2013, at 3:28, Dr. Adam M. Goldstein PhD MSLIS wrote: > On Dec 11, 2012, at 5:17 AM, Christiaan Hofman wrote: > >> This is not consistent. Are the linked files pointing to Papers or >> Papers-old? >> >> And what happens with your .bib file? Is it on the volume where the old >> Papers folder is, and where the Papers-WC will be? Is it also in the >> repository, or outside it? >> >> If it is in the repository, than things should just work, because the >> relative path will always be the same. >> >> Otherwise, you have to make sure that the relative path between the .bib >> file and the papers will remain the same. So starting from a .bib file >> somewhere else on the same volume, this is how it could work. >> >> 0. Records are linked to files in Papers >> 1. Make sure the .bib database is closed and saved >> 2. Papers directory is imported in the repository >> 3. Old Papers directory is removed (moved) >> 4. Create a new working copy (checkout) in the old location Papers >> 5. Open the .bib database >> 6. The records should be linked to the new working copy in the old location, >> as the relative path is the same >> 7. Make sure you save the .bib database to refresh the saved aliases (file >> IDs) >> 8. If you want to put the WC somewhere else, you could *now* (after saving >> and closing) move the Papers to Papers-WC >> 9. Then open the .bib database again, check the links are OK, and save it >> again >> >> Christiaan > > I followed the steps above, or at least, tried my best. It didn't work. The > papers remained linked to the directory called Papers-1 wherever I moved it. In the above I assumed they were linked in the (old) Papers. Not some other place like Papers-1. If they link there, they won't be relinked to some old location, and there's no way to tell them to. So you need to move the folder where they are linked to back to the (old) location first. Or you start the whole thing from Papers-1. > This, even after I deleted the preferences file, selected and re-selected > Papers. Preferences, again, are completely irrelevant for this. that is *only* for auto-filing (looking up is not filing). > I created a disk image and put the Papers-1 directory on it, and then ejected > it, so it could no longer be found. Now none of the PDF's will link to any > folder, including Papers-1, no matter where I move it. > Putting papers on an external volume is dangerous. You cannot just move them there from outside BibDesk, because then BibDesk will loose them. This is because the files won't be moved, but rather they're copied (you can't move between disks, only copy). And then both the file identity and the (absolute and relative) path changes, which means all links are severed. The only way you can do this is if you move *both* the files and the .bib file at the same time (with BibDesk not opening the .bib file), so that the relative paths remain the same. > Any suggestions would be helpful! > > -- > Adam M. Goldstein PhD, MSLIS > -- It is not completely clear where your setup stands at this point. I hope you have a backup (that works), otherwise you may not be able to get the links back. HTH Christiaan -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling question
On Dec 11, 2012, at 5:17 AM, Christiaan Hofman wrote: > This is not consistent. Are the linked files pointing to Papers or Papers-old? > > And what happens with your .bib file? Is it on the volume where the old > Papers folder is, and where the Papers-WC will be? Is it also in the > repository, or outside it? > > If it is in the repository, than things should just work, because the > relative path will always be the same. > > Otherwise, you have to make sure that the relative path between the .bib file > and the papers will remain the same. So starting from a .bib file somewhere > else on the same volume, this is how it could work. > > 0. Records are linked to files in Papers > 1. Make sure the .bib database is closed and saved > 2. Papers directory is imported in the repository > 3. Old Papers directory is removed (moved) > 4. Create a new working copy (checkout) in the old location Papers > 5. Open the .bib database > 6. The records should be linked to the new working copy in the old location, > as the relative path is the same > 7. Make sure you save the .bib database to refresh the saved aliases (file > IDs) > 8. If you want to put the WC somewhere else, you could *now* (after saving > and closing) move the Papers to Papers-WC > 9. Then open the .bib database again, check the links are OK, and save it > again > > Christiaan I followed the steps above, or at least, tried my best. It didn't work. The papers remained linked to the directory called Papers-1 wherever I moved it. This, even after I deleted the preferences file, selected and re-selected Papers. I created a disk image and put the Papers-1 directory on it, and then ejected it, so it could no longer be found. Now none of the PDF's will link to any folder, including Papers-1, no matter where I move it. Any suggestions would be helpful! -- Adam M. Goldstein PhD, MSLIS -- z_california...@shiftingbalance.org http://www.shiftingbalance.org http://www.twitter.com/z_californianus -- http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=180621 -- Associate Editor Reviews Editor Evolution: Education & Outreach http://www.springer.com/life+sci/journal/12052 http://www.twitter.com/EEOblogger -- Spellman 205 (914) 637-2717 (msg) -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 http://www.iona.edu/faculty/agoldstein -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling question
On Dec 11, 2012, at 4:34, Dr. Adam M. Goldstein PhD MSLIS wrote: > > On Dec 10, 2012, at 7:17 PM, Christiaan Hofman wrote: > >> >> On Dec 11, 2012, at 0:04, Dr. Adam M. Goldstein PhD MSLIS wrote: >> >> >>> Now I would like to create a working copy of the directory, and have the >>> records in my bibliography point to the papers in the repository. I am not >>> sure how to do this and I don't want to unlink all of my PDF's :) >>> >> >> Where do they point to now? > > To a folder I named Papers-old Which is the old Papers, which you just renamed? Does it mean that you saved the .bib file after things went wrong? > >> >>> I moved the Papers directory that was uploaded to the repository to >>> Papers-old, and then created a working copy called Papers. I figured that >>> the references in the records would point to the files in the >>> working-copy-Papers directory, which is identical to the initial directory. >> >> What do you mean by "identical"? > > All and only files with the same names as the initial directory. > >> >>> But the records all point to the files in Papers-old. Not what I want. >>> >> >> It may depend on whether you had the .bib file open how it behaves. When the >> database is open, it will try to follow the linked files as they are moved. >> If the .bib file was closed, then after opening it will try to resolve the >> linked files by relative path first, and then by alias. >> >>> I had the thought of selecting all of the records with attached files and >>> telling BibDesk to autofile them, but that ended up moving the linked files >>> into the new directory. I think a new file name was generated as well for >>> the moved file so as not to have the same one as the file already there. I >>> thought it would "re-lilnk" to the files in in the working-copy-Papers >>> directory. >> >> Different files are different files. Why would it re-link to different >> files? Autofile moves files to a unique location, unless it's already there. > > I thought it would just look for files with the same names, in the directory > autofile was set to when they were filed. Neither is true, the first part is only partially true, while the latter is completely untrue. > But, as you suggest, those files are not the same as those the records > originally pointed to. > > So, I think this describes what I want to do. > > 0. Records are linked to files in Papers. > 1. The Papers directory is committed (imported) into the repository. > 2. A new directory called Papers-WC is created by checking out the Papers > directory. It has all and only files in the Papers directory. > 3. Records point to the files in Papers-WC. > > I hope this is more precise…any ideas? > > -- > Adam M. Goldstein PhD, MSLIS > -- This is not consistent. Are the linked files pointing to Papers or Papers-old? And what happens with your .bib file? Is it on the volume where the old Papers folder is, and where the Papers-WC will be? Is it also in the repository, or outside it? If it is in the repository, than things should just work, because the relative path will always be the same. Otherwise, you have to make sure that the relative path between the .bib file and the papers will remain the same. So starting from a .bib file somewhere else on the same volume, this is how it could work. 0. Records are linked to files in Papers 1. Make sure the .bib database is closed and saved 2. Papers directory is imported in the repository 3. Old Papers directory is removed (moved) 4. Create a new working copy (checkout) in the old location Papers 5. Open the .bib database 6. The records should be linked to the new working copy in the old location, as the relative path is the same 7. Make sure you save the .bib database to refresh the saved aliases (file IDs) 8. If you want to put the WC somewhere else, you could *now* (after saving and closing) move the Papers to Papers-WC 9. Then open the .bib database again, check the links are OK, and save it again Christiaan -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling question
On Dec 10, 2012, at 7:17 PM, Christiaan Hofman wrote: > > On Dec 11, 2012, at 0:04, Dr. Adam M. Goldstein PhD MSLIS wrote: > > >> Now I would like to create a working copy of the directory, and have the >> records in my bibliography point to the papers in the repository. I am not >> sure how to do this and I don't want to unlink all of my PDF's :) >> > > Where do they point to now? To a folder I named Papers-old > >> I moved the Papers directory that was uploaded to the repository to >> Papers-old, and then created a working copy called Papers. I figured that >> the references in the records would point to the files in the >> working-copy-Papers directory, which is identical to the initial directory. > > What do you mean by "identical"? All and only files with the same names as the initial directory. > >> But the records all point to the files in Papers-old. Not what I want. >> > > It may depend on whether you had the .bib file open how it behaves. When the > database is open, it will try to follow the linked files as they are moved. > If the .bib file was closed, then after opening it will try to resolve the > linked files by relative path first, and then by alias. > >> I had the thought of selecting all of the records with attached files and >> telling BibDesk to autofile them, but that ended up moving the linked files >> into the new directory. I think a new file name was generated as well for >> the moved file so as not to have the same one as the file already there. I >> thought it would "re-lilnk" to the files in in the working-copy-Papers >> directory. > > Different files are different files. Why would it re-link to different files? > Autofile moves files to a unique location, unless it's already there. I thought it would just look for files with the same names, in the directory autofile was set to when they were filed. But, as you suggest, those files are not the same as those the records originally pointed to. So, I think this describes what I want to do. 0. Records are linked to files in Papers. 1. The Papers directory is committed (imported) into the repository. 2. A new directory called Papers-WC is created by checking out the Papers directory. It has all and only files in the Papers directory. 3. Records point to the files in Papers-WC. I hope this is more precise…any ideas? -- Adam M. Goldstein PhD, MSLIS -- z_california...@shiftingbalance.org http://www.shiftingbalance.org http://www.twitter.com/z_californianus -- http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=180621 -- Associate Editor Reviews Editor Evolution: Education & Outreach http://www.springer.com/life+sci/journal/12052 http://www.twitter.com/EEOblogger -- Spellman 205 (914) 637-2717 (msg) -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 http://www.iona.edu/faculty/agoldstein -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling question
On Dec 11, 2012, at 0:04, Dr. Adam M. Goldstein PhD MSLIS wrote: > Hi all > > I just uploaded my Papers directory to an svn repository. I have the autofile > preference set to put papers there. (To be precise, it's ~/Documents/Papers.) Autofile has absolutely nothing to do with how linked files are found. These preference only affect where autofiling will put the papers. > Now I would like to create a working copy of the directory, and have the > records in my bibliography point to the papers in the repository. I am not > sure how to do this and I don't want to unlink all of my PDF's :) > Where do they point to now? > I moved the Papers directory that was uploaded to the repository to > Papers-old, and then created a working copy called Papers. I figured that the > references in the records would point to the files in the working-copy-Papers > directory, which is identical to the initial directory. What do you mean by "identical"? > But the records all point to the files in Papers-old. Not what I want. > It may depend on whether you had the .bib file open how it behaves. When the database is open, it will try to follow the linked files as they are moved. If the .bib file was closed, then after opening it will try to resolve the linked files by relative path first, and then by alias. > I had the thought of selecting all of the records with attached files and > telling BibDesk to autofile them, but that ended up moving the linked files > into the new directory. I think a new file name was generated as well for the > moved file so as not to have the same one as the file already there. I > thought it would "re-lilnk" to the files in in the working-copy-Papers > directory. Different files are different files. Why would it re-link to different files? Autofile moves files to a unique location, unless it's already there. You really have to be careful to distinguish between file objects and file names. If you replace a file at some path, you get a different file object. If you rename a file, you have the same file object. You are not particularly clear about whether you are talking about paths or file objects in various places, so you have to be more precise. Christiaan > > OK, I don't know if people can follows this. If so, any help would be > appreciated. > > -- > Adam M. Goldstein PhD, MSLIS > -- > z_california...@shiftingbalance.org > http://www.shiftingbalance.org > http://www.twitter.com/z_californianus > -- > http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=180621 > -- > Associate Editor > Reviews Editor > Evolution: Education & Outreach > http://www.springer.com/life+sci/journal/12052 > http://www.twitter.com/EEOblogger > -- > Spellman 205 > (914) 637-2717 (msg) > -- > Dept of Philosophy > Iona College > 715 North Avenue > New Rochelle NY 10801 > http://www.iona.edu/faculty/agoldstein -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling based on Groups
On Aug 12, 2011, at 7:29 PM, Paulo Carreira wrote: > Hi everyone. > > I have found that the filing method that works best for me is to arrange > papers on disk by Subject. I have a top folder named "Papers" with > sub-folders "Papers/Subject A", "Papers/Subject B", ... and so on. I'm a > new user to Bibdesk and I would like to use Autofiling to keep help me keep > my papers on disk with this arrangement. > > < snip > > > I have searched everywhere on Bibdesk's documentation and I found nothing > pointing to this behavior which, IMHO, is a very common way of organizing a > pdf library. Perhaps I'm missing something. Sorry I can't help with your autogeneration syntax question. I have no idea how I would organize my papers by subject, because so many of them fall under so many different subjects. I used to have papers organized by author, but realizing that, as Mike McCracken wrote on this list a while back, "that way lies madness." His advice was to just put all the papers at the top level and "let BibDesk organize them for you." That's what I have started doing. it works well. I use groups of various kinds to organize papers by subjects, authors, or whatever other weird groupings my work requires. So there's my $0.02. Adam -- Adam M. Goldstein PhD, MSLIS -- z_california...@shiftingbalance.org http://www.shiftingbalance.org http://www.twitter.com/shiftingbalance -- http://www.itis.gov/servlet/SingleRpt/SingleRpt?search_topic=TSN&search_value=180621 -- Associate Editor Reviews Editor Evolution: Education & Outreach http://www.springer.com/life+sci/journal/12052 -- Spellman 205 (914) 637-2717 (msg) -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 http://www.iona.edu/faculty/agoldstein -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Whoops, the previous email still contained the debugging code (display dialog). The following removes that. On 2008-02-08, at 2:21 PM, Adam R. Maxwell wrote: > > On Friday, February 08, 2008, at 02:12PM, "Jan Erik Moström" <[EMAIL > PROTECTED] > > wrote: >> Adam R. Maxwell <[EMAIL PROTECTED]> 08-02-08 14.00 >> >>> The old format is unsupported as of 1.3.13. Some of the UI is still >>> present (you can display legacy file/URL icons in the main table), >>> but >>> autofile is only supported in the new scheme. >> >> OK, thanks for the answer. I'll have to think about what to do. >> >>> They're ugly, but they're also ASCII text and harmless in your >>> bibtex >>> file. Non-mac or non-BibDesk users can ignore them >> >> Yep, but it's kind of difficult to see what the referenced file >> is ;-) > > You haven't said exactly what you're trying to accomplish, so I just > guessed at the problem. Do the people you share the BibTeX file > with also have access to the attachments? In that case, you may > want to set up a script hook that copies the autofiled link as a > path for other users. > > In any case, I'd advise you to keep using the aliases for your own > use, rather than replacing them with paths, since that will cause > current and future headaches. Incidentally, other BibDesk users > should also be able to see them as file names in the UI, even if the > files don't exist. Probably your best solution is to use script hooks. The below script will take the path of the latest linked file, remove the directory of the bib file from that path, and paste the relative path of the latest linked file as the local-url field. I have it set to run on autofile. using terms from application "BibDesk" on perform BibDesk action with publications thePubs for script hook theScriptHook tell application "BibDesk" set theField to get field name of theScriptHook as string set newValues to new values of theScriptHook as string if theField is "Local File" then set theDocDir to my getDocDir(document 1) repeat with thePub in thePubs set theValue to my replaceChars(newValues, theDocDir, "") set the value of field "local-url" of thePub to theValue end repeat end if end tell end perform BibDesk action with publications end using terms from on getDocDir(theDoc) tell application "BibDesk" --get the papers path set theDocPath to the path of theDoc as string set theDocName to the name of theDoc as string set theDocDir to my replaceChars(theDocPath, theDocName, "") return theDocDir end tell end getDocDir on replaceChars(this_text, search_string, replacement_string) if this_text contains the search_string then set oldAStid to AppleScript's text item delimiters set AppleScript's text item delimiters to the search_string set the item_list to every text item of this_text set AppleScript's text item delimiters to the replacement_string set this_text to the item_list as string set AppleScript's text item delimiters to oldAStid end if return this_text end replaceChars - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On 2008-02-08, at 2:21 PM, Adam R. Maxwell wrote: > > On Friday, February 08, 2008, at 02:12PM, "Jan Erik Moström" <[EMAIL > PROTECTED] > > wrote: >> Adam R. Maxwell <[EMAIL PROTECTED]> 08-02-08 14.00 >> >>> The old format is unsupported as of 1.3.13. Some of the UI is still >>> present (you can display legacy file/URL icons in the main table), >>> but >>> autofile is only supported in the new scheme. >> >> OK, thanks for the answer. I'll have to think about what to do. >> >>> They're ugly, but they're also ASCII text and harmless in your >>> bibtex >>> file. Non-mac or non-BibDesk users can ignore them >> >> Yep, but it's kind of difficult to see what the referenced file >> is ;-) > > You haven't said exactly what you're trying to accomplish, so I just > guessed at the problem. Do the people you share the BibTeX file > with also have access to the attachments? In that case, you may > want to set up a script hook that copies the autofiled link as a > path for other users. > > In any case, I'd advise you to keep using the aliases for your own > use, rather than replacing them with paths, since that will cause > current and future headaches. Incidentally, other BibDesk users > should also be able to see them as file names in the UI, even if the > files don't exist. Probably your best solution is to use script hooks. The below script will take the path of the latest linked file, remove the directory of the bib file from that path, and paste the relative path of the latest linked file as the local-url field. I have it set to run on autofile. using terms from application "BibDesk" on perform BibDesk action with publications thePubs for script hook theScriptHook tell application "BibDesk" set theField to get field name of theScriptHook as string set newValues to new values of theScriptHook as string if theField is "Local File" then set theDocDir to my getDocDir(document 1) display dialog theDocDir repeat with thePub in thePubs set theValue to my replaceChars(newValues, theDocDir, "") set the value of field "local-url" of thePub to theValue end repeat end if end tell end perform BibDesk action with publications end using terms from on getDocDir(theDoc) tell application "BibDesk" --get the papers path set theDocPath to the path of theDoc as string set theDocName to the name of theDoc as string set theDocDir to my replaceChars(theDocPath, theDocName, "") return theDocDir end tell end getDocDir on replaceChars(this_text, search_string, replacement_string) if this_text contains the search_string then set oldAStid to AppleScript's text item delimiters set AppleScript's text item delimiters to the search_string set the item_list to every text item of this_text set AppleScript's text item delimiters to the replacement_string set this_text to the item_list as string set AppleScript's text item delimiters to oldAStid end if return this_text end replaceChars - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On Friday, February 08, 2008, at 02:12PM, "Jan Erik Moström" <[EMAIL PROTECTED]> wrote: >Adam R. Maxwell <[EMAIL PROTECTED]> 08-02-08 14.00 > >>The old format is unsupported as of 1.3.13. Some of the UI is still >>present (you can display legacy file/URL icons in the main table), but >>autofile is only supported in the new scheme. > >OK, thanks for the answer. I'll have to think about what to do. > >>They're ugly, but they're also ASCII text and harmless in your bibtex >>file. Non-mac or non-BibDesk users can ignore them > >Yep, but it's kind of difficult to see what the referenced file >is ;-) You haven't said exactly what you're trying to accomplish, so I just guessed at the problem. Do the people you share the BibTeX file with also have access to the attachments? In that case, you may want to set up a script hook that copies the autofiled link as a path for other users. In any case, I'd advise you to keep using the aliases for your own use, rather than replacing them with paths, since that will cause current and future headaches. Incidentally, other BibDesk users should also be able to see them as file names in the UI, even if the files don't exist. -- adam - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Christiaan Hofman <[EMAIL PROTECTED]> 08-02-09 00.06 >>These people are running Macs, Windows and Linux/Unix. If we > >If they use BibDesk and use the same relative paths, they can. They don't. OK, now I know. I'll think about how to handle this. jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On 8 Feb 2008, at 11:58 PM, Jan Erik Moström wrote: > Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 23.39 > >> I don't see the problem, as they can simply ignore what they >> see, or get used to it. > > Perhaps I've misunderstood something, so please let me make sure > that I've understood everything correctly. Sorry for being so > tedious, I just want to make sure that I doesn't make any mistakes. > > If I share a references with others, typically using subversion. > These people are running Macs, Windows and Linux/Unix. If we > have set up a repository with the following layout: > > reffile.bib > references/ > file1.pdf > file2.pdf > file3.pdf > etc > > In the bibtex file we use the URL field to contain web urls and > local-url for the path to the PDF. > > If I've now understood things correctly BibDesk will only > generate the "ascii-fied" alias information. The problem as I > see it is that it's not possible for others to actually see what > files that is referenced ... or have I misunderstood something? > > jem > -- > Jan Erik Moström, www.mostrom.pp.se > If they use BibDesk and use the same relative paths, they can. Christiaan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 23.39 >I don't see the problem, as they can simply ignore what they >see, or get used to it. Perhaps I've misunderstood something, so please let me make sure that I've understood everything correctly. Sorry for being so tedious, I just want to make sure that I doesn't make any mistakes. If I share a references with others, typically using subversion. These people are running Macs, Windows and Linux/Unix. If we have set up a repository with the following layout: reffile.bib references/ file1.pdf file2.pdf file3.pdf etc In the bibtex file we use the URL field to contain web urls and local-url for the path to the PDF. If I've now understood things correctly BibDesk will only generate the "ascii-fied" alias information. The problem as I see it is that it's not possible for others to actually see what files that is referenced ... or have I misunderstood something? jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On 8 Feb 2008, at 11:04 PM, Jan Erik Moström wrote: > Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 22.51 > >>> If I understand this correctly, the local-url and url usage will >>> not be supported in the future and if I want to keep the old >>> format then I have to manage this manually. >>> >>> The reason I would like to see this is that when I share the >>> bibtex file with others it would be a bit odd for them to see >>> these fields. >> >> That's why we advice you to remove those using Convert File and >> URL Fields. > Sorry, I meant this about the old style fields. > Do you have an advise on how I should handle the case when I > working with others which can't make any sense of the > 'Bdsk-File-X' field. Am I correct in that I have three alternatives: > > + Not using autofiling and instead fill in local-url and url > fields manually > > + Go back to 1.3.13 and use it as long as I can > > + Not using BibDesk > > jem > -- > Jan Erik Moström, www.mostrom.pp.se I don't see the problem, as they can simply ignore what they see, or get used to it. It gives you many more opportunities. If you're really concerned about sharing you can simply send them a cleaned version by exporting as minimal bibtex. Christiaan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Adam R. Maxwell <[EMAIL PROTECTED]> 08-02-08 14.00 >The old format is unsupported as of 1.3.13. Some of the UI is still >present (you can display legacy file/URL icons in the main table), but >autofile is only supported in the new scheme. OK, thanks for the answer. I'll have to think about what to do. >They're ugly, but they're also ASCII text and harmless in your bibtex >file. Non-mac or non-BibDesk users can ignore them Yep, but it's kind of difficult to see what the referenced file is ;-) jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 22.51 >>If I understand this correctly, the local-url and url usage will >>not be supported in the future and if I want to keep the old >>format then I have to manage this manually. >> >>The reason I would like to see this is that when I share the >>bibtex file with others it would be a bit odd for them to see >>these fields. > >That's why we advice you to remove those using Convert File and >URL Fields. Do you have an advise on how I should handle the case when I working with others which can't make any sense of the 'Bdsk-File-X' field. Am I correct in that I have three alternatives: + Not using autofiling and instead fill in local-url and url fields manually + Go back to 1.3.13 and use it as long as I can + Not using BibDesk jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On Friday, February 08, 2008, at 01:28PM, "Jan Erik Moström" <[EMAIL PROTECTED]> wrote: >I tried finding an answer to this in the archive and the manual >but I couldn't find anything definitive, sorry if I missed something. > >I've been using the local-file url to hold a reference to the >PDF to the paper. This has worked well and have allowed my to >share the references (through subversion) with others (non-mac, >non-bibdesk users). Now when I played around with 1.3.14 it adds >the Bdsk-File-1 and Bdsk-Url-1 fields for converted records >while keeping the original local-url and url fields. > >For new records the local-urls and url fields are not generated >when I drag a file to a record. This is expected behavior (i.e. works as designed). >I understand the rationale for doing this, but is there a way to >keep the old behavior, that is creating a local-url field and >use the url field? And not generating the Bdsk-File/Bdsk-Url fields. No. You can probably set up a script hook to copy the file/URL to another field as a text path. > From the mailing list: >>The Local-Url field is deprecated, and it does not use auto-file >>anymore. You're strongly encouraged to clear all your Local-Url fields >>and switch exclusively to the new file icon view in the side pane. >-- >>Sure, you can still use it. Just the more advanced support like >>opening the URL won't be supported. You can always easily convert the >>Url field to a linked URL. >If I understand this correctly, the local-url and url usage will >not be supported in the future and if I want to keep the old >format then I have to manage this manually. The old format is unsupported as of 1.3.13. Some of the UI is still present (you can display legacy file/URL icons in the main table), but autofile is only supported in the new scheme. >The reason I would like to see this is that when I share the >bibtex file with others it would be a bit odd for them to see >these fields. They're ugly, but they're also ASCII text and harmless in your bibtex file. Non-mac or non-BibDesk users can ignore them, and they should round-trip through subversion just fine. The group information that BibDesk (or JabRef) saves in a BibTeX file looks odd as well, but it's still a valid BibTeX file. -- adam - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On 8 Feb 2008, at 10:28 PM, Jan Erik Moström wrote: > I tried finding an answer to this in the archive and the manual > but I couldn't find anything definitive, sorry if I missed something. > > I've been using the local-file url to hold a reference to the > PDF to the paper. This has worked well and have allowed my to > share the references (through subversion) with others (non-mac, > non-bibdesk users). Now when I played around with 1.3.14 it adds > the Bdsk-File-1 and Bdsk-Url-1 fields for converted records > while keeping the original local-url and url fields. > > For new records the local-urls and url fields are not generated > when I drag a file to a record. > > I understand the rationale for doing this, but is there a way to > keep the old behavior, that is creating a local-url field and > use the url field? And not generating the Bdsk-File/Bdsk-Url fields. > And this has also been answered many times. > From the mailing list: >> The Local-Url field is deprecated, and it does not use auto-file >> anymore. You're strongly encouraged to clear all your Local-Url >> fields >> and switch exclusively to the new file icon view in the side pane. > -- >> Sure, you can still use it. Just the more advanced support like >> opening the URL won't be supported. You can always easily convert the >> Url field to a linked URL. > If I understand this correctly, the local-url and url usage will > not be supported in the future and if I want to keep the old > format then I have to manage this manually. > > The reason I would like to see this is that when I share the > bibtex file with others it would be a bit odd for them to see > these fields. > > > > jem > -- > Jan Erik Moström, www.mostrom.pp.se That's why we advice you to remove those using Convert File and URL Fields. Christiaan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
I tried finding an answer to this in the archive and the manual but I couldn't find anything definitive, sorry if I missed something. I've been using the local-file url to hold a reference to the PDF to the paper. This has worked well and have allowed my to share the references (through subversion) with others (non-mac, non-bibdesk users). Now when I played around with 1.3.14 it adds the Bdsk-File-1 and Bdsk-Url-1 fields for converted records while keeping the original local-url and url fields. For new records the local-urls and url fields are not generated when I drag a file to a record. I understand the rationale for doing this, but is there a way to keep the old behavior, that is creating a local-url field and use the url field? And not generating the Bdsk-File/Bdsk-Url fields. From the mailing list: >The Local-Url field is deprecated, and it does not use auto-file >anymore. You're strongly encouraged to clear all your Local-Url fields >and switch exclusively to the new file icon view in the side pane. -- >Sure, you can still use it. Just the more advanced support like >opening the URL won't be supported. You can always easily convert the >Url field to a linked URL. If I understand this correctly, the local-url and url usage will not be supported in the future and if I want to keep the old format then I have to manage this manually. The reason I would like to see this is that when I share the bibtex file with others it would be a bit odd for them to see these fields. jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
In order to understand why Christiaan might have written his reply in a somewhat harsher tone, you should search the archives of this list and see how often we had this question in the last weeks. It becomes annoying to have to write the same answers and explanations over and over again. Good luck, Alex Am 08.02.2008 um 21:13 schrieb Jan Erik Moström: > Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 20.59 > >> Read the alert you get and don't complain. Unique for a cite >> key is not unique for a file. > > Since I'm so *incredible stupid* then you could perhaps explain > why a unique city key wouldn't generate a unique file name when > I use it in the file name specifier? > > jem > -- > Jan Erik Moström, www.mostrom.pp.se > > > -- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Bibdesk-users mailing list > Bibdesk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-users > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Alexander H. Montgomery <[EMAIL PROTECTED]> 08-02-08 12.28 >Because if you attach more than one file to a given >publication, they can't be named the same thing. Hence the >file name specifier requires a unique specifier in addition to >the cite key. OK, I didn't realize that it was possible to add more than one file. jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
On Friday, February 08, 2008, at 12:14PM, "Jan Erik Moström" <[EMAIL PROTECTED]> wrote: >Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 20.59 > >>Read the alert you get and don't complain. Unique for a cite >>key is not unique for a file. > >Since I'm so *incredible stupid* then you could perhaps explain >why a unique city key wouldn't generate a unique file name when >I use it in the file name specifier? This has been discussed repeatedly and in some detail on the mailing list since 1.3.13 was released: http://www.mail-archive.com/bibdesk-users@lists.sourceforge.net/msg01769.html hth, adam - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
And that's just a tip of the iceberg, though the main reason we now enforce it. A cite key is generated unique *within the items of a document*, while a file name is generated unique *in your file system*. These are completely different criteria. Moreover, when a file name is generated, there is no guarantee that the cite key is actually generated as a 'unique' key in *any* sense. Christiaan On 8 Feb 2008, at 9:28 PM, Alexander H. Montgomery wrote: > Because if you attach more than one file to a given publication, they > can't be named the same thing. Hence the file name specifier requires > a unique specifier in addition to the cite key. > > -AHM > > On 2008-02-08, at 12:13 PM, Jan Erik Moström wrote: > >> Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 20.59 >> >>> Read the alert you get and don't complain. Unique for a cite >>> key is not unique for a file. >> >> Since I'm so *incredible stupid* then you could perhaps explain >> why a unique city key wouldn't generate a unique file name when >> I use it in the file name specifier? >> >> jem >> -- >> Jan Erik Moström, www.mostrom.pp.se >> >> >> - >> >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ >> ___ >> Bibdesk-users mailing list >> Bibdesk-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bibdesk-users >> > > > -- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Bibdesk-users mailing list > Bibdesk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Because if you attach more than one file to a given publication, they can't be named the same thing. Hence the file name specifier requires a unique specifier in addition to the cite key. -AHM On 2008-02-08, at 12:13 PM, Jan Erik Moström wrote: > Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 20.59 > >> Read the alert you get and don't complain. Unique for a cite >> key is not unique for a file. > > Since I'm so *incredible stupid* then you could perhaps explain > why a unique city key wouldn't generate a unique file name when > I use it in the file name specifier? > > jem > -- > Jan Erik Moström, www.mostrom.pp.se > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Bibdesk-users mailing list > Bibdesk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-users > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Christiaan Hofman <[EMAIL PROTECTED]> 08-02-08 20.59 >Read the alert you get and don't complain. Unique for a cite >key is not unique for a file. Since I'm so *incredible stupid* then you could perhaps explain why a unique city key wouldn't generate a unique file name when I use it in the file name specifier? jem -- Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] Autofiling
Read the alert you get and don't complain. Unique for a cite key is not unique for a file. Sigh. Christiaan On 8 Feb 2008, at 8:41 PM, Jan Erik Moström wrote: > I just downloaded and launched 1.3.14, and it complained that my > naming for autofiling wouldn't generate a unique name. I've been > using "%f{Cite Key}%e", why doesn't this generate a unique name? > The cite key is unique. > > jem > -- > Jan Erik Moström, www.mostrom.pp.se - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] autofiling format string %b
great, thx a. Am 27.01.2008 um 19:17 schrieb Christiaan Hofman: > > On 27 Jan 2008, at 6:00 PM, Alex Hamann wrote: > >> Just did my switch to the new local-file system (yes, I am late) and >> everything is nice and smooth. Just one problem arises for me: >> my autofile preferences were >> %b/%p1/%f{Cite Key}%u0%e >> the option Papers folder location was checked and set to ~/Library/ >> texmf/bibtex/bib/BibDesk files >> this resulted in a Preview of: >> ~/Library/texmf/bibtex/bib/BibDesk files/Document File Name/ >> McCracken/ >> citeKey.pdf >> >> (I know that there are strong arguments in support of having only one >> single bib file and thus also only one single folder for the attached >> files. Still, since my 5 bib files are containing entries concerned >> with strictly different subjects I want to keep them apart and also >> keep the respective attached files in respective folders.) >> >> Now under 1.3.14 with the same settings the Preview gives me this: >> ~/Library/texmf/bibtex/bib/BibDesk files/path/to/document/McCracken/ >> citeKey.pdf >> >> Notice the different meaning of %b: in the first case "Document File >> Name" and "path/to/Document" in the latter. >> There seems to be no way to get the setting I had before the update, >> is this intentional or could we get a specifier for Document File >> Name again? >> >> Cheers, >> >> Alex > > Sorry for that, it's a bug. We seem to use the wrong part of the path > now. That will be fixed in the next nightly. > > > Christiaan > > > > -- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Bibdesk-users mailing list > Bibdesk-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-users > = please avoid sending me word attachements; see http://www.gnu.org/philosophy/no-word-attachments.html for details and background - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] autofiling format string %b
On 27 Jan 2008, at 6:00 PM, Alex Hamann wrote: > Just did my switch to the new local-file system (yes, I am late) and > everything is nice and smooth. Just one problem arises for me: > my autofile preferences were > %b/%p1/%f{Cite Key}%u0%e > the option Papers folder location was checked and set to ~/Library/ > texmf/bibtex/bib/BibDesk files > this resulted in a Preview of: > ~/Library/texmf/bibtex/bib/BibDesk files/Document File Name/McCracken/ > citeKey.pdf > > (I know that there are strong arguments in support of having only one > single bib file and thus also only one single folder for the attached > files. Still, since my 5 bib files are containing entries concerned > with strictly different subjects I want to keep them apart and also > keep the respective attached files in respective folders.) > > Now under 1.3.14 with the same settings the Preview gives me this: > ~/Library/texmf/bibtex/bib/BibDesk files/path/to/document/McCracken/ > citeKey.pdf > > Notice the different meaning of %b: in the first case "Document File > Name" and "path/to/Document" in the latter. > There seems to be no way to get the setting I had before the update, > is this intentional or could we get a specifier for Document File > Name again? > > Cheers, > > Alex Sorry for that, it's a bug. We seem to use the wrong part of the path now. That will be fixed in the next nightly. Christiaan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users