Add rules for TeX packages (e)ledmac and (e)ledpar. References from manuals:
eledmac p. 46:
> Each section will read and write an associated "line-list file", containing information used to do the numbering; the file will be called `<jobname>.nn`, where `nn` is the section number. However, you may direct that an extra string be added before the `nn` in that filename, in order to distinguish these temporary files from others: that string is called `\extensionchars`. Initially it's empty, since different operating systems have greatly varying ideas about what characters are permitted in file names. So `\renewcommand{\extensionchars}{-}` gives temporary files called `<jobname>.-1`, `<jobname>.-2`, etc.
eledmac p. 112:
> Endnotes of all varieties are saved up in a file, typically named `<jobname>.end`.
eledpar p.8:
> The `\beginnumbering` macro resets the line number to zero, reads an auxiliary file called `<jobname>.nn` (where `<jobname>` is the name of the main input file for this job, and `nn` is 1 for the first numbered section, 2 for the second section, and so on), and then creates a new version of this auxiliary file to collect information during this run. Separate auxiliary files are maintained for right hand texts and these are named `<jobname>.nnR`, using the ‘R’ to distinguish them from the left hand and serial (non-parallel) texts.
Without the asterisk at the end of the directory's path, an exception for
a file within this directory does not work.
(ex. !packages/repositories.config)
This reverts commit 0fb0fbefa5.
Restore the Xcode rules to the Objective-C template as per the discussion
thread on 5bd4330. Although the rules correspond to an IDE and so are
global, most users of the Obj-C template expect to find the Xcode rules
in the template generated by github.com, since the IDE is so ubiquitous.
This could possibly be resolved by adding a template transclusion
mechanism in the future, but for now duplication is the way to go.
.DCU (Delphi Compiled Unit) files are binary files that are used between compiling source (text) and linking the executable. They're created by the compiler, joined together in memory, combined with the startup code and put into an actual executable (.EXE/.DLL/.BPL) by the linker
Support for Phalcon, a PHP Framework
Manually fixed up the rules in the original PR to be consistent with our
omission of the trailing asterisk elsewhere. Fixes#846.
The original ignore was far too general and results in eliminating packages
named "db" or "project", for example. These are not that uncommon for package
names. Fixes#921.
