1
0
mirror of https://github.com/github/gitignore synced 2024-12-23 21:30:46 +01:00
Carl Suster 792a95ef29 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.
2014-04-14 13:41:01 +10:00
2014-03-27 17:04:56 +01:00
2013-08-15 03:18:55 +02:00
2012-04-20 10:12:43 +02:00
2012-08-08 11:36:30 +03:00
2011-02-21 18:02:55 -08:00
2013-10-06 14:40:01 +02:00
2014-03-08 00:45:00 -08:00
2014-03-31 11:49:00 +08:00
2014-03-27 17:04:56 +01:00
2014-03-24 17:14:52 +01:00
2012-08-15 01:43:20 +02:00
2013-11-19 17:36:12 +05:30
2014-03-27 17:04:56 +01:00
2011-08-17 00:55:26 -05:00
2011-02-01 06:03:02 +08:00
2013-07-19 11:44:46 -04:00
2013-02-01 13:27:15 +01:00
2014-02-27 21:51:51 -05:00
2014-01-18 10:29:50 +01:00
2013-07-25 06:18:55 -07:00
2011-08-02 21:36:51 +01:00
2010-11-09 04:49:58 +08:00
2014-02-13 15:57:44 +02:00
2014-03-31 02:52:46 +02:00
2014-01-30 21:15:45 -02:00
2010-11-23 09:36:53 +08:00
2012-03-03 02:08:17 +01:00
2014-04-08 18:48:50 +03:00
2014-03-09 14:35:00 +09:00
2013-01-07 21:25:52 -08:00
2013-11-12 15:09:20 +07:00
2014-03-06 10:07:26 +02:00
2014-03-16 23:04:52 -07:00
2014-02-27 06:45:11 -06:00
2014-04-04 16:25:30 -06:00
2013-09-18 10:20:26 +02:00
2014-03-07 00:15:40 +11:00
2013-11-20 20:13:07 +01:00
2013-12-17 15:06:57 +08:00
2013-10-06 14:40:01 +02:00
2012-07-31 11:57:21 +08:00
2011-02-21 18:03:04 -08:00
2014-03-27 17:04:56 +01:00
2010-11-22 17:54:05 -08:00
2013-10-21 16:20:37 +11:00

A collection of .gitignore templates

This is GitHubs collection of .gitignore file templates. We use this list to populate the .gitignore template choosers available in the GitHub.com interface when creating new repositories and files.

For more information about how .gitignore files work, and how to use them, the following resources are a great place to start:

Folder structure

The files in the root directory are for .gitignore templates that are project specific, such as language or framework specific templates. Global (operating system or editor specific) templates should go into the Global/ directory.

Contributing guidelines

Wed love you to help us improve this project. To help us keep this collection high quality, we request that contributions adhere to the following guidelines.

  • Provide a link to the application or projects homepage. Unless its extremely popular, theres a chance the maintainers dont know about or use the language, framework, editor, app, or project your change applies to.

  • Provide links to documentation supporting the change youre making. Current, canonical documentation mentioning the files being ignored is best. If documentation isnt available to support your change, do the best you can to explain what the files being ignored are for.

  • Explain why youre making a change. Even if it seems self-evident, please take a sentence or two to tell us why your change or addition should happen. Its especially helpful to articulate why this change applies to everyone who works with the applicable technology, rather than just you or your team.

  • Please consider the scope of your change. If your change specific to a certain language or framework, then make sure the change is made to the template for that language or framework, rather than to the template for an editor, tool, or operating system.

  • Please only modify one template per pull request. This helps keep pull requests and feedback focused on a specific project or technology.

In general, the more you can do to help us understand the change youre making, the more likely well be to accept your contribution quickly.

Please also understand that we cant list every tool that ever existed. Our aim is to curate a collection of the most common and helpful templates, not to make sure we cover every project possible. If we choose not to include your language, tool, or project, its not because its not awesome.

Contributing workflow

Heres how we suggest you go about proposing a change to this project:

  1. Fork this project to your account.
  2. Create a branch for the change you intend to make.
  3. Make your changes to your fork.
  4. Send a pull request from your forks branch to our master branch.

Using the web-based interface to make changes is fine too, and will help you by automatically forking the project and prompting to send a pull request too.

License

MIT.

Description
No description provided
Readme
Languages
Markdown 100%