<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Jan 26, 2006, at 10:25 AM, Alan Schussman wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">So what do I write into the value field of the TM_LATEX_BIB variable? Do I need to write in the path or only the file name?</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <BR></BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">At this point, it needs the full path to the bib file. I wonder if the script could use the same method that bibtex uses (kpsewhich?) to find the file. That doesn't seem necessary when using TM_LATEX_BIB, because that's a variable specific to OSX/TextMate -- so no cross-platform worries there. But, needing to specify the full path when using a \bibliography{} <BR></FONT></P></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV>in the \bibliography{} thing you should not have to specify the full path, only the relative path, relative to the directory of the current file, and you shouldn't even need to put the .bib at the end.</DIV><DIV>TM_LATEX_BIB needs the full path.</DIV><DIV><BR><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">command is potentially something that could break cross-platform compatibility of the .tex file itself, or would pose problems if one were to move the local texmf tree for some reason. I'm not entirely familiar with how the innards of that file-finding actually work, but eventually being able to search the texmf tree would probably be a good way to go about it.</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P></BLOCKQUOTE>That is true, but it is a bit more elaborate than what I want to go into right now. I guess I keep my bib file near the corresponding tex file. Where do other people keep their bib files? I could try to come up with a better search, but I don't really know where I should be looking.<BR><BLOCKQUOTE type="cite"><BR><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Will this also work, if I use "footcite" for citing? And what would the shortcut be for this way of completion? The same as before (Cmd-Esc)?</FONT></P> <BR></BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">I think only \cite works right now, but it would be ideal if we could complete footcite as well as the cite commands from natbib (citet, citep, citeyear, etc).</FONT></P></BLOCKQUOTE></DIV><DIV><FONT class="Apple-style-span" color="#0000DD"><BR class="khtml-block-placeholder"></FONT></DIV>This is just a question of adding \footcite to the list of commands that give you the scope meta.cite.latex.<DIV>I just wasn't aware of it. I'll add it later today when I update things.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This is still a work in progress, so thank you all for your patience and feedback.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Let me mention here as well the extra new completion commands, that work by pressing escape, when the scope is either labels or bibliography respectively. In order to run those, you need to do and svn update on the global Support directory, which should reside under ~/Library/Application Support/TextMate/Support</DIV><DIV>There are three new files in the bin subfolder of that, whose names start with "Latex".</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Btw, the BibDesk completion command will not be deleted, just "deprecated" in the sense that a new bibliography completion command will be constructed, and I personally will work mostly on that one, apart from fixing the problems I am currently aware of with the bibDesk one (thanks Attilio). Anyone with shell scripting knowledge is welcome to improve on it.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>@Christian: I'd rather not use the .aux file, since it is not always up to date. I might however try to make the script look at all \include{}'s also.</DIV><DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Haris</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN> </DIV><BR></DIV></BODY></HTML>