https://github.com/briochemc/texmf
Science Score: 23.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
✓Committers with academic emails
1 of 1 committers (100.0%) from academic institutions -
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (10.3%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: briochemc
- Language: TeX
- Default Branch: master
- Size: 668 KB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
texmf
This repo stores all the LaTeX files that I use for every article/project. This repo should be particularly useful to reproduce the same .pdf outputs without too many migraines when trying to compile from another machine.
It also has the unique .bib file that I will keep using and updating here.
I should check that the class (.cls) and bibliographic-style (.bst) files required by journals are up to date.
The texmf/ directory and the following tree were manually created (and did not came to life just by installing TexLive). That is, I had to build the tree below (using mkdir) and copy/download the files myself from the command-line interface (CLI).
Tree:
texmf
├── bibtex
│ ├── bib
│ │ └── all_my_references_BP.bib
│ └── bst
│ └── agufull08.bst
└── tex
└── latex
└── local
└── agujournal.cls
The texmf directory should be located in ~/Library
To Do
- [ ] Test on other machines
- [ ] Test multiple .bst files
- [ ] Test multiple .cls files
Notes
The directory tree of a LaTeX article should be like below, and authors should open the manuscript where it is (i.e., cd to where manuscript.tex is).
Do not have a subdirectory for the manuscript!
This is because when compiling, epstopdf only has the right to write in subfolders (e.g., cannot write in ../figures) and will only be able to convert .eps to .pdf if the current working directory is parent to the figures/ directory.
.
├── figures
│ ├── ... (pdf converted files)
│ ├── figure_1_for_example-eps-converted-to.pdf
│ └── figure_1_for_example.eps
├── ... (auxiliary files, .pdf, .aux, .log, .etc)
└── manuscript.tex
Cheat Sheet for my vim/skim setup for LaTeX
If all is installed correctly: - gvim for editor - skim for viewer - vimtex plugin for LaTeX stuff
I should be able to do the following:
Backward search
In skim, press CMD-SHIFT-click and gvim should point to the corresponding point in the .tex.
(You need to set up the "sync" settings in Skim properly for that — Instructions for the setting are in the vimtex help, accessible from vim via :h vimtex)
Forward search
In gvim, when in normal mode (not in insert mode) press ,r and skim should point to the corresponding point in the .pdf.
Owner
- Name: Benoît Pasquier
- Login: briochemc
- Kind: user
- Location: Sydney, Australia
- Company: UNSW
- Website: https://www.bpasquier.com/
- Repositories: 157
- Profile: https://github.com/briochemc
Research Associate at UNSW
GitHub Events
Total
Last Year
Committers
Last synced: about 2 years ago
Top Committers
| Name | Commits | |
|---|---|---|
| Benoit Pasquier | p****b@u****u | 82 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: over 1 year ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0