├── .github └── ISSUE_TEMPLATE │ ├── bug_report.yml │ ├── config.yml │ └── enhancement_or_feature_request.yml ├── CONTRIBUTING.md └── README.md /.github/ISSUE_TEMPLATE/bug_report.yml: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | description: Create a bug report to help fix a problem with the Sublime Text core. 4 | body: 5 | - type: textarea 6 | attributes: 7 | label: Description of the bug 8 | description: | 9 | A description of what the bug is. 10 | 1. Make sure that you first check if your bug hasn't already been reported. It saves a bit of work on our end. 11 | 2. Please attach screenshots if they help in understanding the problem better. Don't host your images/videos/GIFs somewhere (e.g. Imgur) and share a link. Directly drag & drop here to avoid navigating to an external link. 12 | 3. Make sure to format any code samples using triple backticks. If the code sample happens to be large, share a gist/pastebin link instead. 13 | validations: 14 | required: true 15 | - type: textarea 16 | attributes: 17 | label: Steps to reproduce 18 | description: "Please provide detailed steps on how the bug can be reproduced. Make sure to start ST in [safe mode](https://www.sublimetext.com/docs/safe_mode.html#) before jotting down the reproduction steps." 19 | placeholder: | 20 | 1. Start ST in safe mode. 21 | 2. Second step. 22 | 3. Third step. 23 | validations: 24 | required: true 25 | - type: textarea 26 | attributes: 27 | label: Expected behavior 28 | description: "A description of what you expected to happen." 29 | validations: 30 | required: true 31 | - type: textarea 32 | attributes: 33 | label: Actual behavior 34 | description: "A description of what actually happened." 35 | validations: 36 | required: true 37 | - type: input 38 | attributes: 39 | label: Sublime Text build number 40 | placeholder: "e.g. 4107 - type 'Help: About' in the Command Palette" 41 | validations: 42 | required: true 43 | - type: input 44 | attributes: 45 | label: Operating system & version 46 | placeholder: "e.g. macOS 10.14, Windows 10, Ubuntu 18.04" 47 | validations: 48 | required: true 49 | - type: input 50 | attributes: 51 | label: (Linux) Desktop environment and/or window manager 52 | placeholder: "e.g. Gnome, LXDE, i3" 53 | - type: textarea 54 | attributes: 55 | label: Additional information 56 | description: "You can jot down any additional information you consider relevant to the bug report." 57 | placeholder: | 58 | Examples could include 59 | 60 | 1. Information on some hardware you are using. 61 | 2. Are you using additional monitors ? 62 | 3. If the bug report happens to be GIT/VCS related, share what version of GIT or Sublime Merge you are using. 63 | 4. NTFS related issues could include details on the NTFS you are using. 64 | 65 | You get the idea. 66 | - type: textarea 67 | attributes: 68 | label: OpenGL context information 69 | description: "If your bug has something to do with hardware acceleration, then please share the OpenGL context information (which can be found by scrolling to the top of ST's console. You can open the console by pressing ctrl + `). You can find more information on ST's hardware acceleration feature [here](https://www.sublimetext.com/docs/gpu_rendering.html)." 70 | placeholder: | 71 | It should look something like the following 72 | 73 | OpenGL Context Information: 74 | GL API Version: 4.6.0 - Build 26.20.100.7870 75 | GLSL Version: 4.60 - Build 26.20.100.7870 76 | Vendor: Intel 77 | Renderer: Intel(R) UHD Graphics 78 | render: plain -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | contact_links: 3 | - name: Syntax highlighting bug report 4 | url: https://github.com/sublimehq/Packages/issues/new/choose 5 | about: Create a bug report over at the Packages repository, if you are facing syntax highlighting issues with any of the syntax packages that are shipped by default with Sublime Text. -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/enhancement_or_feature_request.yml: -------------------------------------------------------------------------------- 1 | --- 2 | name: Enhancement or feature request 3 | description: Suggest an enhancement or feature for Sublime Text core. 4 | body: 5 | - type: textarea 6 | attributes: 7 | label: Problem description 8 | description: | 9 | A description of a problem, workflow or integration that your suggestion would solve. If the problem is OS specific, include that information here. 10 | 11 | Make sure that you first check if your feature/enhancement request hasn't already been reported. It saves a bit of work on our end. 12 | validations: 13 | required: true 14 | - type: textarea 15 | attributes: 16 | label: Preferred solution 17 | description: "A description of what changes should be made to Sublime Text to solve the problem." 18 | validations: 19 | required: true 20 | - type: textarea 21 | attributes: 22 | label: Alternatives 23 | description: "A description of any alternative solutions or enhancements considered." 24 | validations: 25 | required: true 26 | - type: textarea 27 | attributes: 28 | label: Additional Information 29 | description: | 30 | If applicable, add screenshots to help demonstrate the problem or proposed solution. Code examples or related links are useful, too. 31 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Before creating a new issue 2 | 3 | * **This tracker is for issues with the Sublime Text *Core* only.** 4 | 5 | This includes packages providing core functionality, such as `Default` or `Color Scheme - Default`, but excludes packages providing support for syntaxes/languages. 6 | 7 | For language-specific issues with the "Default Language Packages" (which handle syntax highlighting and other language-related things), refer to the [Default Language Packages repository](https://github.com/sublimehq/Packages). 8 | 9 | For issues related to other packages, head over to the respective repository or contact its author. 10 | Start with a [clean profile](http://www.sublimetext.com/docs/revert.html) if you need to verify. 11 | 12 | * Search for the issue [here](https://github.com/sublimehq/sublime_text/issues) to check if it was already reported. 13 | You may use [labels](https://github.com/sublimehq/sublime_text/labels) for filtering the issue list by clicking any of these related to the problem you want to report or request. 14 | 15 | 16 | ## Filing a bug 17 | 18 | 1. Start with a descriptive but concise **subject** that quickly and uniquely identifies the problem. 19 | 1. Write a **summary** of the problem in a few lines, giving an idea of what the issue is about. 20 | 1. Then, **describe** the bug with all the information you can give. 21 | Be sure to include the following information: 22 | * Operating System 23 | * The version of Sublime Text that you're using 24 | * Any related software which may cause ST to act strangely 25 | 26 | Also keep in mind to clearly separate fact from speculation. 27 | 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. **if a specific code produces the bug, try to share the code** 28 | 1. Workarounds or other related tips on how to avoid the issue are welcome. 29 | 30 | We won't slaughter you if you can't fulfill all of these steps but prepare to answer a few question if we think we're lacking information. 31 | 32 | 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. 33 | 34 | 35 | ## Filing an enhancement or a feature request 36 | 37 | 1. Start with a descriptive but concise **subject** that quickly and uniquely identifies the issue. 38 | 1. Explain briefly what the enhancement is and why you think it would be useful. 39 | 1. Provide any other necessary or useful information regarding your issue, such as (code) examples or related links. 40 | 41 | Note: "enhancements" are modifications to existing behavior as opposed to something entirely new. 42 | 43 | --- 44 | 45 | This is a bug tracker run by the community. For the initial idea, read this forum thread: http://www.sublimetext.com/forum/viewtopic.php?f=2&t=12095. 46 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Sublime Text - Core - Bug and Issue Tracker 2 | 3 | ## The issue list 4 | 5 | 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. 6 | 7 | Use [Github's reactions feature](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) to vote on issues. 8 | Simple "+1" comments with no further content will be deleted without notice. 9 | 10 | You can also use [labels](https://github.com/sublimehq/sublime_text/labels) to filter the list of issues. 11 | 12 | ## Before creating a new issue 13 | 14 | * **This tracker is for issues with the Sublime Text *Core* only.** 15 | 16 | This includes packages providing core functionality, such as `Default` or `Color Scheme - Default`, but excludes packages providing support for syntaxes/languages. 17 | 18 | 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). 19 | 20 | * 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. 21 | 22 | ## Filing a bug 23 | 24 | 1. Start with a descriptive but concise **subject** that quickly and uniquely identifies the problem. 25 | 1. Write a **summary** of the problem in a few lines, giving an idea of what the issue is about. 26 | 1. Then, **describe** the bug with all the information you can give. 27 | Be sure to include the following information: 28 | * Operating System 29 | * The version of Sublime Text that you're using 30 | * Any related software which may cause ST to act strangely 31 | * If relevant, does the bug occur with no packages installed / [with ST in safe mode](https://www.sublimetext.com/docs/safe_mode.html)? 32 | 33 | Also keep in mind to clearly separate fact from speculation. 34 | 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. 35 | 1. Workarounds or other related tips on how to avoid the issue are welcome. 36 | 37 | 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. 38 | 39 | 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. 40 | 41 | ## Filing an enhancement or a feature request 42 | 43 | 1. Start with a descriptive but concise **subject** that quickly and uniquely identifies the issue. 44 | 1. Explain briefly what the enhancement is and why you think it would be useful. 45 | 1. Provide any other necessary or useful information regarding your issue, such as (code) examples or related links. 46 | 47 | Note: "enhancements" are modifications to existing behavior as opposed to something entirely new. 48 | 49 | --- 50 | 51 | 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) 52 | and has since been adopted by Sublime Hq. 53 | --------------------------------------------------------------------------------