overleaf / overleaf/overleaf

Feature request: Allow for a local texmf directory inside each project

Open
#429 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
18.1k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Description

I often have the problem, that i need to add my own packages to my projects. Recently I've migrated from placing them inside ~/texmf to project-dir/texmf, so that they, in their current version, are placed alongside my project files. This way I avoid tedious work when trying to get an older project from a few years back to compile again with the newer package versions in case version upgrades caused incompatibility with the old api.

Now I'd like something like that for my sharelatex projects. Aside from the fact, that uploading my texmf tree via manually creating folders one after the other and then uploading files per folder doesn't sound like fun,

http://tex.stackexchange.com/questions/34203/where-to-put-sty-and-cls-file-for-project

, specifically the first answer concerning TEXMFHOME=texmf, should easily provide a solution, should the choice be to include this feature. Note that is says: "For a local texmf tree you do not need to run texhash because files are searched recursively in that tree". On my linux system this works just as described here!

Thanks for all your hard work!

Just a quick question at the end: Would it theoretically be possible to have multiple texlive versions installed? I often face the problem of older projects not being compatible with newer texlive versions, so it would be great, if i could just keep the older versions somehow and have the texlive-version dropdown menu in the project settings. (Just read something concerning an issue report a while back concerning a thesis, that wasn't compilable because of incompatibility/breaking of a package due to texlive upgrade to version 2014. This is just such a case, where people perhaps are in a hurry, have a deadline, and can't afford to spend hours searching the web for some strange new bug they never heard of before.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing the project compilation configuration and how TeX Live versions are selected; clarify whether local texmf support and multiple TeX Live versions are both in scope, then define completion criteria for each.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.