ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Issues

by SublimeText ST2/ST3 Removed

The official bug tracking for Sublime Text, powered by us.

Details

Installs

  • Total 80
  • Win 36
  • OS X 26
  • Linux 18
Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
OS X 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sublime Text Bug and Issue Tracker

Before writing a new issue, search for it please, to check if it is already reported. Please fill bug reports, we encourage you to log properly every bug you found.

This is a bug tracker run by the community. For the inital idea, read this forum thead: http://www.sublimetext.com/forum/viewtopic.php?f=2&t=12095.

The issue list

Head straight to https://github.com/SublimeText/Issues/issues for a list of all issues or click Issues in the navigation bar above.

Before creating a new issue

  • Make sure it isn't a package that's causing the bug. Start with a clean profile if you need.

    This repo is for Sublime Text-related bugs only. If your issue is related to a specific package or plugin, submit your report to that package's repository instead.

  • Search for the bug here to see if an issue like yours already exists. You may use labels for filterting the issue list by clicking any of these related to the problem you want to report.

Filing a bug

  1. Start with a descriptive but concise subject that quickly and uniquely identifies the problem.
  2. Write a summary of the problem in a few lines, giving an idea of what the issue is about.
  3. 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

    Also keep in mind to clearly separate fact from speculation.

  4. 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

  5. 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 question if we think we're lacking information.

If you want to be really good at reporting bugs you can also read these guidelines 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.
  2. Explain briefly what the enhancement is and why you think it would be useful.
  3. Provide any other necessary or useful information regarding your issue, such as (code) examples or related links.

Note: “enhancements” are modifications to existing behaviour as opposed to something entirely new.