GithubHelp home page GithubHelp logo

Comments (9)

tpoisot avatar tpoisot commented on May 19, 2024

I've looked at the code, and I think the solution is fairly simple. Line 91 in latex_cite_compl.py already checks the location of the documents. It's just a matter of looking for it in $TEXMF/bibtex/bib.

from latextools.

msiniscalchi avatar msiniscalchi commented on May 19, 2024

Thanks, I ll look into this. M
On Aug 12, 2012 3:18 AM, "Timothée Poisot" [email protected] wrote:

I've looked at the code, and I think the solution is fairly simple. Line
91 in latex_cite_compl.py already checks the location of the documents.
It's just a matter of looking for it in $TEXMF/bibtex/bib.


Reply to this email directly or view it on GitHubhttps://github.com//issues/60#issuecomment-7671929.

from latextools.

apc avatar apc commented on May 19, 2024

This is related to issue 47.

from latextools.

cwwwu avatar cwwwu commented on May 19, 2024

@msiniscalchi: I can have a look at this. Should we also consider being able to disable cite completion on a per-project basis in case the user doesn't wish to see all of the bib entries from external bib files?

from latextools.

msiniscalchi avatar msiniscalchi commented on May 19, 2024

I'm not sure. Right now cite completion only works on files that are
actually referenced in the tex file(s). There should be no need for project
management, right? Unless you mean that your project can determine whether
it's OK to look for bib files in the local texmf tree or not... But I don't
see why this should be configurable per-project.

My "ideal" would be for the plugin to do pretty much what tex&friends do.
So, if indeed bibtex looks in the texmf tree, then so should the plugin.
But I don't see this as a high-priority item: keep in mind that the plugin
has to work across platforms and tex distributions, and getting things
right is usually a big headache

On Fri, Sep 7, 2012 at 10:54 AM, Wallace Wu [email protected]:

@msiniscalchi https://github.com/msiniscalchi: I can have a look at
this. Should we also consider being able to disable cite completion on a
per-project basis in case the user doesn't wish to see all of the bib
entries from external bib files?


Reply to this email directly or view it on GitHubhttps://github.com//issues/60#issuecomment-8369521.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

from latextools.

cwwwu avatar cwwwu commented on May 19, 2024

About the per-project thing, I was considering the latter (determining whether or not it's okay to look for bib files in the local texmf tree), but that was with the mindset that the plugin would manage the directories to search that are specified in sublime-settings files, but the ideal solution you have in mind probably doesn't require this extra layer of user intervention/configuration.

I'm not sure if the shell commands kpsewhich -var-value TEXMFHOME (gets the local texmf directory path) and/or kpsewhich -var-value BIBINPUTS (returns the directories that bibtex searches for bib files) would be sufficient to determine whether or not to search the local texmf tree when performing cite completion.

p.s. I'm interested in working on this plugin some more. Are there any (higher-priority) features/fixes that I can look into?

from latextools.

marktani avatar marktani commented on May 19, 2024

What is the status of this issue? Having the same exact issue here.

Edit:
As apc mentioned, #47 is a possible workaround. That fixes the problem for me.

from latextools.

richard-herron avatar richard-herron commented on May 19, 2024

The work around works, but is there any way to hard code this? I think the LaTeX standard is to keep personal .bib, .bst, .cls, and .sty files in the texmf folder. The linked issue (#47) mentions a hard code solution via texfiledir, but in my ST3 LaTeXTools this is commented out. Is there a way that I can hard code this? Or add a personal settings?

Thanks! (I hope I don't sound ungrateful, I'm just getting started with ST3 after a long time on Vim and want to make sure that I don't start off on day one with a nest of ../../../../../../ that I have to reverse engineer every time. :) ).

from latextools.

ig0774 avatar ig0774 commented on May 19, 2024

This was fixed quite a while ago now.

from latextools.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.