![]() So my texmf tree is in phd\Resources\tools\localtexmf\. Its not a great system, but it is simple. I just have one git rep for all my PhD work, with a bunch of folders. One repo for all work, including the texmftree Then when ever you work on a new computer check out the repo from git, and tell your tex distribution to know about the local texmf tree. Better than an absolute or a relative path. Then when you go to work in a project you just add \bibliography and it will find it. tex file to make an annotated bibliography) (I also have my JabRef XML setting in this directory, and a. Put your master.bib file in localtexmf\bibtex\bib\master_bibliography\master.bib. Once you have created that tree, add it to git. Create a local texmf tree in Ubuntu (TexLive).Create a local texmf tree in MiKTeX (Windows). ![]() How to setup a local tex tree is beyond the scope of this answer but it isn't hard. Its also very useful as many conferences and journals distribute their own templates and styles not through CTAN, but just as. The local texmf tree means that you never have to use absolute, or even relative paths for your bibliography. What you would like is a local texmf tree, which in in one git repo.Ī local texmf tree is for putting various package-like-artifacts, that are not proper packages managed through your package manager (e.g. In answer to sub Q1: this is an excellent idea (even if I do say so myself) The alternative is to use git subtree, I don't use it, but I suppose the concept of this workflow can be adapted to use subtree instead of submodule. In the git world there has been a long-standing discussion whether submodule is a good thing or not. That extra remote might not migrate well across computers (due to different file paths), but since it's just there "in case of no network", I don't mind it too much. This allows me to also push/pull to the main repository when I don't have network access. That extra remote points to the location of my main bibliography repository. ![]() While my approach normally relies on bitbucket, I also like to add another remote in the submodule. So you should already feel comfortable with git before you use this a workflow. Git submodules make your document repository – and how to work with it – more complicated.When you add many references, you end up pushing and pulling quite often: push from the main one, pull in the document.everything can be done using relative paths, so, it is portable across computers, users, OSes.you can tweak the bibliography that are specific to one document and not push them back to the main repository,.you can transfer changes from your main "bib" repository to each document, or the other way around,.your bibliography is versioned, so you can easily track what exact version of a BIB file you used,.I think there are a few advantages to this general approach: The proper way is to tinker with BST files and the like, but in the heat of the moment it's often a lot faster to just tweak the "biblio" module of a paper. how the authors are formatted, don't show URLs in the bibliography for a paper. However, in some cases I just want to change e.g. Typically, I try to only edit my main BIB repository (that's the only one that is loaded within JabRef for me), push those changes to bitbucket and then pull in the changes from within each document repository. In you document you can then just specify to use the BIB files in that directory. In each of my papers and thesis, I use git submodule add biblio to make a submodule directory with my document. For this repository, I also have a private remote at BitBucket for convenience and portability. So I have one repository "bib" that contains my BibTeX files. ![]() I use the approach detailed in for my own work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |