Home · Extensions · ._exrc

`._exrc`

2 claimants 0 primary 2 secondary secondary-only

Confirm or correct this extension

Existing claims are only secondary or weakly-attested. A confirmation (or correction) would strengthen the catalog. Vocabulary reference: docs/extension_labels.md.

Quick pick — proposed PLs. Tick one or more to auto-fill the label as pl/<id>. Each chip is a PL that upstream sources or Linguist heuristics already suggest for ._exrc. Multi-tick for a polysemous extension.

vim pl/vim via pygments · secondaryVim script pl/vim-script via pygments · secondary

Label * If label has <...>, fill it here (e.g. for pl/<id> type rust). For multi-PL submissions, enter several pl/<id> separated by commas. Friendly name (optional) Reference URL (optional, but recommended — spec / Wikipedia / vendor) Evidence / notes *

— or, if the button is blocked, use the link just below:

(fill the form to enable this link)

What happens after I submit?

A new GitHub issue is opened in this repo with your form contents in a structured YAML block and the label ext-review. Your GitHub login becomes the annotator; the issue's created_at is the submission timestamp.
A curator script (tools/process_extension_labels.py) fetches all ext-review issues and writes their parsed contents into data/derived/extension_labels.csv with curator_status="new". Until this script runs, your submission lives only as the GitHub issue.
Your submission shows up on the curator triage page (/review/curator/) under "new". Maintainers review the issue (comment, ask for clarification, accept or reject) and edit extension_labels.csv to set curator_status to accepted.
For pl/<id> labels, build_pl_taxonomy.py promotes accepted labels into ext_claim.csv with source="manual_review:<your-login>" and strength="proposed". The next site rebuild then shows your claim on this extension's page and on the language's page.
Friendly-name + reference-URL labels (e.g. binary:image for .png) are not promoted into ext_claim.csv (they aren't PL claims) but are surfaced on this page's "Prior labels" table so anyone landing here sees them next to the auto-detected category.

In short: submitting opens an issue (provenance), and a small ingestion pipeline turns issues into rows the site renders. The loop is currently manual (the curator script must be run by a maintainer); GitHub Actions could automate it on each new issue.

Claimants (2)

Languages that list ._exrc among their extensions. Strength reflects whether the upstream source treated it as their primary extension.

Language	Source	Strength
vim	pygments	secondary
Vim script	pygments	secondary

SWH-mined examples (0)

No archived examples for ._exrc in our local mirror yet.