Hello everyone,
I am heavily using the latex bundle currently and the bibliography completion does not seem to work anymore. When trying to complete ~ \citep{Foo} I get 100% CPU usage by ruby and these messages after killing it:
/Library/Application Support/TextMate/Bundles/Latex.tmbundle/Support/ lib/LaTeXUtils.rb:141:in `parse_bibfile': Interrupt from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:116:in `map' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:116:in `parse_bibfile' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:251:in `cite_scan' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:248:in `each' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:248:in `cite_scan' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:216:in `call' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:216:in `recursive_scan' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:215:in `each' ... 8 levels... from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:204:in `recursive_scan' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:255:in `cite_scan' from /Library/Application Support/TextMate/Bundles/Latex.tmbundle/ Support/lib/LaTeXUtils.rb:63:in `get_citations' from /tmp/temp_textmate.Bb9x12:8
I am using the latest version of BibDesk to manage my bibfile, which inserts quite a lot of non bibtex code in custom fields e.g.
@article{McCafferty2002ME, Author = {McCafferty, S and Bermingham, E and Quenouille, Brice and Planes, Serge and Hoelzer, G and Asoh, K}, Date-Modified = {2008-01-27 17:23:40 +0100}, Filed = {Yes}, Journal = {Molecular Ecology}, Pages = {1377--1392}, Read = {No}, Title = {Historical biogeography and molecular systematics of the {I}ndo-{P}acific genus \textit{{D}acyllus} ({T}eleostei: {P}omacentridae)}, Volume = {11}, Year = {2002}, Bdsk-File-1 = {YnBsaXN0MDDUAQIDBAUGCQpYJHZlcnNpb25UJHRvcFkkYXJjaGl2ZXJYJG9iamVjdHMSAAG GoNEHCFRyb290gAFfEA9OU0tleWVkQXJjaGl2ZXKoCwwXGBkdJCVVJG51bGzTDQ4PEBEUViR jbGFzc1dOUy5rZXlzWk5TLm9iamVjdHOAB6ISE4ACgAOiFRaABIAGWWFsaWFzRGF0YVxyZWx hdGl2ZVBhdGjSDRobHFdOUy5kYXRhgAVPEQLMAAAAAALMAAIAAANtYWMAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAADCsBfOSCsAAAAQSwYfTWNDYWZmZXJ0eTIwMDItSGlzdG8jMTA0QkFELnB kZgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBLrb2LoXgAAAAAAAAAAAABAAM AAAkgAAAAAAAAAAAAAAAAAAAABnBhcGVycwAQAAgAAMKv +64AAAARAAgAAL2LhVgAAAABABQAEEsGABBGCwAQRggAB/ PvAABwQgACAEhtYWM6VXNlcnM6amlobzpXb3JrOmJpYmxpb2dyYXBoaWU6cGFwZXJzOk1jQ2 FmZmVydHkyMDAyLUhpc3RvIzEwNEJBRC5wZGYADgDwAHcATQBjAEMAYQBmAGYAZQByAHQAeQ AyADAAMAAyAC0ASABpAHMAdABvAHIAaQBjAGEAbAAgAGIAaQBvAGcAZQBvAGcAcgBhAHAAaAB5ACAAYQBuAGQAIABtAG8AbABlAGMAdQBsAGEAcgAgAHMAeQBzAHQAZQBtAGEAdABpAGMAcwAgAG8AZgAgAHQAaABlACAASQBuAGQAbwAtAFAAYQBjAGkAZgBpAGMAIABnAGUAbgB1AHMAIABEAGEAYwB5AGwAbAB1AHMAIAAoAFQAZQBsAGUAbwBzAHQAZQBpAC8AIABQAG8AbQAuAHAAZABmAA8ACAADAG0AYQBjABIAnFVzZXJzL2ppaG8vV29yay9iaWJsaW9ncmFwaGllL3BhcGVycy9NY0NhZmZlcnR5MjAwMi1IaXN0b3JpY2FsIGJpb2dlb2dyYXBoeSBhbmQgbW9sZWN1bGFyIHN5c3RlbWF0aWNzIG9mIHRoZSBJbmRvLVBhY2lmaWMgZ2VudXMgRGFjeWxsdXMgKFRlbGVvc3RlaTogUG9tLnBkZgATAAEvAAAVAAIAC///AADSHh8gIVgkY2xhc3Nlc1okY2xhc3NuYW1loyEiI11OU011dGFibGVEYXRhVk5TRGF0YVhOU09iamVjdF8QfnBhcGVycy9NY0NhZmZlcnR5MjAwMi1IaXN0b3JpY2FsIGJpb2dlb2dyYXBoeSBhbmQgbW9sZWN1bGFyIHN5c3RlbWF0aWNzIG9mIHRoZSBJbmRvLVBhY2lmaWMgZ2VudXMgRGFjeWxsdXMgKFRlbGVvc3RlaTogUG9tLnBkZtIeHyYnoicjXE5TRGljdGlvbmFyeQAIABEAGgAfACkAMgA3ADoAPwBBAFMAXABiAGkAcAB4AIMAhQCIAIoAjACPAJEAkwCdAKoArwC3ALkDiQOOA5cDogOmA7QDuwPEBEUESgRNAAAAAAAAAgEAAAAAAAAAKAAAAAAAAAAAAAAAAAAABFo=}}
The last large chunk is a Finder alias to a file on the disk, wich allows to store many files associated with each reference. Could that be preventing the ruby script to parse the file? Anyone with the same setup?
BTW, the completion method involving bibdesk directly (through applescripts) still works but is slower and requires mouse clicks.
Thanks in advance.
NB: this was already sent to textmate-dev but is probably more appropriate here
JiHO --- http://jo.irisson.free.fr/
On Friday, March 14, 2008, at 09:37AM, "jiho" jo.irisson@gmail.com wrote:
BTW, the completion method involving bibdesk directly (through applescripts) still works but is slower and requires mouse clicks.
There's another solution using BibDesk that's linked here:
http://bibdesk.sourceforge.net/wiki/index.php/Other_Applications
It should be really fast, and has reasonably good searching heuristics (disclaimer: I wrote it, so I'm biased). The .tmCommand needs a minor fix, but my iDisk isn't cooperating at the moment. E-mail me if you want the fix.
On 2008-March-14 , at 19:45 , Adam R. Maxwell wrote:
On Friday, March 14, 2008, at 09:37AM, "jiho" jo.irisson@gmail.com wrote:
BTW, the completion method involving bibdesk directly (through applescripts) still works but is slower and requires mouse clicks.
There's another solution using BibDesk that's linked here:
http://bibdesk.sourceforge.net/wiki/index.php/Other_Applications
It should be really fast, and has reasonably good searching heuristics (disclaimer: I wrote it, so I'm biased). The .tmCommand needs a minor fix, but my iDisk isn't cooperating at the moment. E- mail me if you want the fix.
Works fast and reliably indeed. Two caveats though: - Bibdesk was running but the bib file not opened. the command opened it (I have one set as default) but probably did not wait long enough and returned with the message "this command should be used with bibdesk 1.3.0" etc - the second time, I closed the bib file again but since bibdesk was active it took less time to reopen it. however nothing happened after that in textmate (no completion propositions, no error/warning message)
I'll use this from now on (and still try to figure what makes the ruby parser choke on my file, it may be the symptom of a deeper issue). Thanks a lot.
JiHO --- http://jo.irisson.free.fr/
On Friday, March 14, 2008, at 03:00PM, "jiho" jo.irisson@gmail.com wrote:
- Bibdesk was running but the bib file not opened. the command opened
it (I have one set as default)
It should also parse the .tex file and figure out what .bib file to open, as well. No guarantee of reliability though :).
but probably did not wait long enough and returned with the message "this command should be used with bibdesk 1.3.0" etc
That's odd. It tries repeatedly for 10 seconds to establish a connection to BibDesk, which should be plenty of time. That message is only displayed if the connection fails but some version of BibDesk is running, so the assumption is that it's an old version.
- the second time, I closed the bib file again but since bibdesk was
active it took less time to reopen it. however nothing happened after that in textmate (no completion propositions, no error/warning message)
If you can reproduce that, please follow up with me off-list so I can fix the problems if possible. I only use it occasionally these days, so it doesn't get much testing on my part.
I'll use this from now on (and still try to figure what makes the ruby parser choke on my file, it may be the symptom of a deeper issue).
Even valid BibTeX is really hard to parse correctly, unfortunately.
On Friday, March 14, 2008, at 04:15PM, "Adam R. Maxwell" amaxwell@mac.com wrote:
On Friday, March 14, 2008, at 03:00PM, "jiho" jo.irisson@gmail.com wrote:
- the second time, I closed the bib file again but since bibdesk was
active it took less time to reopen it. however nothing happened after that in textmate (no completion propositions, no error/warning message)
If you can reproduce that, please follow up with me off-list so I can fix the problems if possible. I only use it occasionally these days, so it doesn't get much testing on my part.
Never mind. I have a fix for that and I'll post back when I've uploaded it.
thanks, adam
On Mar 14, 2008, at 4:34 PM, Adam R. Maxwell wrote:
Never mind. I have a fix for that and I'll post back when I've uploaded it.
Source and binary for the BibDesk completion stuff should be fixed now, and the .tmCommands should work after making the required modifications (see the README file).
http://bibdesk.sourceforge.net/wiki/index.php/Other_Applications
On 2008-March-15 , at 00:14 , Adam R. Maxwell wrote:
On Friday, March 14, 2008, at 03:00PM, "jiho" jo.irisson@gmail.com wrote:
- Bibdesk was running but the bib file not opened. the command opened
it (I have one set as default)
It should also parse the .tex file and figure out what .bib file to open, as well. No guarantee of reliability though :).
OK. since I am using multiple files I was not sure it would find it. Anyway I only have one master bib file for now.
but probably did not wait long enough and returned with the message "this command should be used with bibdesk 1.3.0" etc
That's odd. It tries repeatedly for 10 seconds to establish a connection to BibDesk, which should be plenty of time. That message is only displayed if the connection fails but some version of BibDesk is running, so the assumption is that it's an old version.
well it seems 10 sec was not long enough for me, the machine was quite crowed with other processes at this time ;) Offtopic: overall, Bibdesk takes quite some time to load since the switch to the new file linking system. I really like it but it seems more resources intensive. FYI my bib file contains just over 500 refs, weights 1.2Mb (hell that's a lot for text!) and I am using Bibdesk on a macbook with 1Gb of RAM. I guess the only remedy would be to drop bibtex as a storage format but maybe there's something wrong on my end.
- the second time, I closed the bib file again but since bibdesk was
active it took less time to reopen it. however nothing happened after that in textmate (no completion propositions, no error/warning message)
If you can reproduce that, please follow up with me off-list so I can fix the problems if possible. I only use it occasionally these days, so it doesn't get much testing on my part.
I'll use this from now on (and still try to figure what makes the ruby parser choke on my file, it may be the symptom of a deeper issue).
Even valid BibTeX is really hard to parse correctly, unfortunately.
Charilaos Skiadas is investigating this. I corrected as much as I could in the bib file (no more warnings in bibdesk). The minimal bibtex exported from bibdesk work so it is definitely something related to the other, more custom, fields. I'm guessing some strange character in an abstract copied form a PDF but can't find it. Since there are probably a large proportion of TM+LaTeX users that also use BibDesk it would be nice to know what fails.
Thanks for your help and your work,
JiHO --- http://jo.irisson.free.fr/
-
Adam R. Maxwell -
jiho