overleaf / overleaf/overleaf

Feature request : keep some pdfs in the folder structure

Open
#1,085 0 comments 0 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'm teaching LaTeX to my students using Overleaf. And when it comes to building images using TikZ with the standalone package, I have to explain that it is more complicated on Overleaf compared to local compiling because we have to download the compiled pdf image and then upload it back to Overleaf. And this has to be repeated after every compilation.

I know that we could put the image into another project and then import the compiled result directly, but this is not acceptable to me because I want all my students' work in a single project (so that it can be easily assessed).

It would be great if you could add a parameter to specify which resulting PDF should be kept in the Overleaf folder structure. This could be done in a number of ways:

  • Using a config file;
  • Adding a menu parameter next to the other parameters;
  • Look for a comment at the beginning of the document, which could be something like % Overleaf: keep pdf.

It would also be nice to have some reasonable defaults. For example, keep all pdf of tex files that are in the images folder and/or all that use the standalone package.

Thanks for considering my request.

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

No files, tests, or entry points are named. Start by locating the PDF compilation and cleanup flow, then compare how configuration, menu parameters, or document comments could identify PDFs to retain. Done means a selected PDF remains in the project folder after compilation, including the proposed images and standalone-package cases.

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
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.