emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Ken Mankoff <mankoff@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org + git branches for derived files
Date: Fri, 13 Aug 2021 20:53:06 +0000	[thread overview]
Message-ID: <87bl616p8t.fsf@posteo.net> (raw)
In-Reply-To: <87czqh5gt1.fsf@gmail.com> (Ken Mankoff's message of "Fri, 13 Aug 2021 11:40:42 -0700")

Hi Ken,

Ken Mankoff writes:

> I'd like to keep derivative products (the LaTeX output, the final PDF,
> etc.) available in Git, but not commit those changes each time I
> change the Org file. Perhaps git-annex as appropriate for this, but
> seems over-kill.
> Is there some way to mostly-seamlessly commit the LaTeX and/or PDF
> and/or other files to their own git branches but in a way that
> overwrites the history of that branch, so that a small Org file that
> generates a big binary PDF does not pollute the git tree?

There are probably better solutions, but maybe this could help you:
use org-publish (which also works when the output is LaTeX/PDF, and
not only with HTML). See https://orgmode.org/manual/Publishing.html

You should have to define a new publishing project and declare a
directory for the PDFs derivatives, applying a value to
:publishing-directory, and configure in this directory a second git
repository, only for PDFs. The value of :publishing-function keyword
should be `org-latex-publish-to-pdf'.

Best regards,

Juan Manuel 

  reply	other threads:[~2021-08-13 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 18:40 Org + git branches for derived files Ken Mankoff
2021-08-13 20:53 ` Juan Manuel Macías [this message]
2021-08-13 23:10 ` Tim Cross
2021-08-14  0:53 ` Mark Barton
2021-08-14  1:53   ` Rob Sargent
2021-08-14  3:44     ` Rob Sargent
2021-08-14  4:21       ` Samuel Wales
2021-08-16  1:02         ` Ken Mankoff
2021-08-16  4:58           ` Rob Sargent
2021-08-31 12:21 ` Timothy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bl616p8t.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).