# Sublime Text - Core - Bug and Issue Tracker

## The issue list

Head straight to https://github.com/sublimehq/sublime_text/issues for a list of all issues or click `Issues` in the navigation bar on the almost-top.

Use [Github's reactions feature](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) to vote on issues.
Simple "+1" comments with no further content will be deleted without notice.

You can also use [labels](https://github.com/sublimehq/sublime_text/labels) to filter the list of issues.

## Before creating a new issue

* **This tracker is for issues with the Sublime Text *Core* only.**

    This includes packages providing core functionality, such as `Default` or `Color Scheme - Default`, but excludes packages providing support for syntaxes/languages.
    
    For language-specific issues with the "Default Packages" (which handle syntax highlighting and other language-related things), refer to the [Default Packages repository](https://github.com/sublimehq/Packages).

* Search for the issue [here](https://github.com/sublimehq/sublime_text/search?q=&type=Issues) to check if it was already reported. You may use labels for filtering the [issue list](https://github.com/sublimehq/sublime_text/issues) by clicking any of these related to the problem you want to report or request.

## Filing a bug

1.  Start with a descriptive but concise **subject** that quickly and uniquely identifies the problem.
1.  Write a **summary** of the problem in a few lines, giving an idea of what the issue is about.
1.  Then, **describe** the bug with all the information you can give.
    Be sure to include the following information:
    * Operating System
    * The version of Sublime Text that you're using
    * Any related software which may cause ST to act strangely
    * If relevant, does the bug occur with no packages installed / [with ST in safe mode](https://www.sublimetext.com/docs/safe_mode.html)?

    Also keep in mind to clearly separate fact from speculation.
1.  Try to find a way to **reproduce** the problem and write down precise steps. It might be useful to include a *code example* for this.
1.  Workarounds or other related tips on how to avoid the issue are welcome.

We won't slaughter you if you can't fulfill all of these steps, but prepare to answer a few questions if we think we're lacking information.

If you want to be really good at reporting bugs, you can also read [these guidelines](https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html) for bugzilla bugs.

## Filing an enhancement or a feature request

1.  Start with a descriptive but concise **subject** that quickly and uniquely identifies the issue.
1.  Explain briefly what the enhancement is and why you think it would be useful.
1.  Provide any other necessary or useful information regarding your issue, such as (code) examples or related links.

Note: "enhancements" are modifications to existing behavior as opposed to something entirely new.

---

This bug tracker was [initiated by the community](http://web.archive.org/web/20150524043750/https://www.sublimetext.com/forum/viewtopic.php?f=2&t=12095)
and has since been adopted by Sublime Hq.