Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Per man gitignore there are four sources of patterns for ignoring files. Command-line arguments are probably too much hassle; .gitignore is itself version-controlled (unless you include .gitignore ...
Answer
#1: Initial revision
by
Peter Taylor
·
2022-01-06T17:11:08Z (almost 3 years ago)
Per [man gitignore](https://git-scm.com/docs/gitignore) there are four sources of patterns for ignoring files. Command-line arguments are probably too much hassle; `.gitignore` is itself version-controlled (unless you include `.gitignore` in it), which creates complications. That leaves `$GIT_DIR/info/exclude` and the file listed in config variable `core.excludesFile`. Sadly, it seems that `$GIT_DIR/info/exclude` has to be a file and not a directory whose contents are concatenated. A somewhat complicated solution which probably doesn't conflict directly with anything you're already doing would be: 1. Create a script which updates `$GIT_DIR/info/exclude` to list the .pdf files for which there are .tex files. If you want to be really cautious you could delimit a section of the file with comments and replace only that section. 2. [`alias`](https://ss64.com/bash/alias.html) `git` to invoke the script and then pass the arguments along to `/usr/bin/git`. (In practice this probably means making the script itself pass the arguments along, and make the script the alias).