Code Monkey home page Code Monkey logo

Comments (4)

msiniscalchi avatar msiniscalchi commented on July 29, 2024

This is a tricky issue. At one level, you can already set the output directory by passing the appropriate option to the tex engine (either in Settings or as a %!TEX magic comment). This will work. However, the code that parses the log file and displays the PDF file will fail because these files will not, in general, be in the expected location (i.e., in the same dir as the tex source or root file).

The painful issue to deal with is that MikTeX and TeXLive handle this differently. MikTeX offers more granular control--you can tell it to put aux files in one directory and the pdf output file in another. TeXLive, on the other hand, only allows you to say "all generated files go to directory X"---which applies to both PDF and aux files. So, one, you need code that handles both cases separately, which is painful. Second, you can't provide the exact same functionality on MikTeX and TeXLive.

I'm thinking about an alternative approach: introduce a setting or magic comment that points to the log and pdf files, wherever they may be. This is easy to do and cross-platform. Users who want to fiddle with where tex puts generated files are sophisticated enough to understand what such settings would mean.

Happy to entertain alternatives, but so far this is what I could come up with!

from atom-latextools.

cortner avatar cortner commented on July 29, 2024

I actually like having everything in an alternative out directory. Do I understand correctly that the forward/backward search won't work?

from atom-latextools.

ig0774 avatar ig0774 commented on July 29, 2024

Forward search (or even displaying the PDF) definitely won't. You'll lose any relevant warnings or errors in the console because latextools won't be able to read the log file and the delete temp files functionality will likely do nothing useful. Oddly, backward search may work perfectly, since that mostly depends on a corresponding synctex file.

from atom-latextools.

cortner avatar cortner commented on July 29, 2024

too bad - this would be a nice feature to have, because a lot of my collaborators who haven't yet accepted Git will collaboratively work on a latex document on dropbox and we screw up each others compilations.

from atom-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.