Carl Suster [Mon, 14 Apr 2014 03:41:01 +0000 (13:41 +1000)]
Merge pull request #1008 from maieul/master
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.
Revert "Packages folder is ignored correctly".
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)
Carl Suster [Sun, 6 Apr 2014 00:38:40 +0000 (10:38 +1000)]
Merge branch 'fix-1022'
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.
ONion [Mon, 31 Mar 2014 03:07:06 +0000 (11:07 +0800)]
add delphi .dcu
.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
Namik Nuhanovic [Mon, 31 Mar 2014 00:52:46 +0000 (02:52 +0200)]
Add 'pom.xml.versionsBackup'
'mvn versions:use-latest-versions' generates 'pom.xml.versionsBackup' file, because '-DgenerateBackupPoms=true' is default; see http://mojo.codehaus.org/versions-maven-plugin/use-latest-versions-mojo.html#generateBackupPoms
notbear [Mon, 24 Mar 2014 16:14:52 +0000 (17:14 +0100)]
Fixes uncomplete CTools
Ignoring cache/ makes also necessary files ignored:
modules/ctools/page_manager/plugins/cache/page_manager_context.inc
modules/ctools/plugins/cache/simple.inc
modules/ctools/plugins/cache/export_ui.inc
Torben Werner [Fri, 21 Mar 2014 01:46:27 +0000 (12:46 +1100)]
Increase the specificity of PlayFramework rules
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.
John Munkhoff [Tue, 18 Mar 2014 23:21:03 +0000 (16:21 -0700)]
Add Global/SlickEdit.gitignore file
This commit adds a global ignore file for SlickEdit, a commercial editor.
SlickEdit will create the following files when the user sets up a workspace:
*.vpw Workspace file. Contains a list of project files associated with
the workspace.
*.vpj Project file. Contains the project’s settings, including the list
of source files.
*.vpwhist Workspace history file for Windows. Contains user session
information (list of open files, debugger breakpoints, etc.)
*.vpwhistu Workspace history file for UNIX/Linux/MacOSX. (Same as above.)
*.vtg Workspace tag file. Contains a database of source code symbols.
It is assumed that GitHub users will generally not want to store their
workspace and project files in a repository, so those files are ignored
globally. However, those files do not contain user-specific data so they
could be stored in a repository and shared among developers if desired for
a particular project. This can be done by adding rules like ’!*.vpw’ and
‘!*.vpj’ to the project’s .gitignore file.
The workspace history and tag files contain user-specific data, so they
should not be stored in a repository.
For more information, download the PDF user guide from:
http://www.slickedit.com/products/slickedit/product-documentation
Note: The user guide is 1400 pages long and over 13MB in size.
Searching for ‘vpwhist’ will lead to the section that discusses storing
these files in a repository.
John Munkhoff [Mon, 17 Mar 2014 06:04:52 +0000 (23:04 -0700)]
Update Qt.gitignore
- Ignore '*.moc' files (foo.moc created when foo.cpp contains a Q_OBJECT.)
- Ignore '/.qmake.cache' and '/.qmake.stash' as does the official Qt Creator project.
Devon Carew [Sat, 8 Mar 2014 08:45:00 +0000 (00:45 -0800)]
Update Dart.gitignore
- add the `build/` directory to the .gitignore list (now created by pub).
- add the `.dart.precompiled.js` files (created by dart2js) to the ignore list.
hugovk [Thu, 6 Mar 2014 08:07:26 +0000 (10:07 +0200)]
Ignore coverage results
coverage.py creates HTML reports in the htmlcov directory (this tool can also be used with coveralls.io)
http://nedbatchelder.com/code/coverage/
https://pypi.python.org/pypi/coverage
These aren't really common patterns in the Node world, and if a Node project includes one of these types as files, they're as likely to want to include them in the project as not (`*.csv` is as likely to be a data source as `*.json`).