Re: Org + git branches for derived files

Hi Ken, It’s been a while, but just to chime in: if you use GitHub you may find to be of use. Let me know if you have any questions, I wrote it a few months ago. Ken Mankoff writes: > Hello, > > I think this might be more of a git question than

Re: Org + git branches for derived files

> On Aug 15, 2021, at 7:02 PM, Ken Mankoff wrote: > > Hi All, > > Thank you for the suggestions. > > I think the most elegant solution is to have a hook on GitHub that compiles > the PDF on a remote server. But it takes a lot more work, because I don't > necessarily have *everything* in G

Re: Org + git branches for derived files

Hi All, Thank you for the suggestions. I think the most elegant solution is to have a hook on GitHub that compiles the PDF on a remote server. But it takes a lot more work, because I don't necessarily have *everything* in Git - my local 'library.bib' usually isn't included, nor my custom emacs

Re: Org + git branches for derived files

it is an interesting question as many things go into the product: - org file - your .el files - org version - emacs version - os - hw - export commands run so the desire to keep the product is understandable. not only is it effort to find the export commands run, but other stuff might change out

Re: Org + git branches for derived files

> On Aug 13, 2021, at 7:53 PM, Rob Sargent wrote: > > > >> On Aug 13, 2021, at 6:54 PM, Mark Barton wrote: >> >> Ken, >> >> You could consider using git-lfs, Large File Support. There is some setup >> and then you can say track *.pdf and that will tell git to track the binary >> file i

Re: Org + git branches for derived files

> On Aug 13, 2021, at 6:54 PM, Mark Barton wrote: > > Ken, > > You could consider using git-lfs, Large File Support. There is some setup and > then you can say track *.pdf and that will tell git to track the binary file > in a more efficient way. I use this mailing for csv files that I wan

Re: Org + git branches for derived files

Ken, You could consider using git-lfs, Large File Support. There is some setup and then you can say track *.pdf and that will tell git to track the binary file in a more efficient way. I use this mailing for csv files that I want to have a snapshot version of with the Jupyter notebook that used

Re: Org + git branches for derived files

Ken Mankoff writes: > Hello, > > I think this might be more of a git question than an Org question, but I > imagine > I might find the answer here and that it might be useful to others, so I ask > here. > > I'd like to keep derivative products (the LaTeX output, the final PDF, etc.) > availabl

Re: Org + git branches for derived files

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-seamless

Org + git branches for derived files

Hello, I think this might be more of a git question than an Org question, but I imagine I might find the answer here and that it might be useful to others, so I ask here. I'd like to keep derivative products (the LaTeX output, the final PDF, etc.) available in Git, but not commit those changes