rDr4g0n/JsDebuggr

Issues

• This plugin doesn't seem to be working

  #33 opened 6 years ago
  1

• Need Help

  #31 opened 7 years ago
  1

• The right-click menu of the jsdebugger doesn't work

  #30 opened 7 years ago
  3

• The add breakpoint option is not enabled sometimes

  #29 opened 7 years ago
  1

• Tests!

  #28 opened 8 years ago
  0

• Multi-selection support

  #27 opened 8 years ago
  0

• Click on gutter to add and remove breakpoints

  #26 opened 8 years ago
  0

• Dont check point scope for every option on right click

  #25 opened 8 years ago
  0

• More efficient `is_enabled` checks for commands

  #24 opened 8 years ago
  0

• In order for plugin to work it's requiring that the JsDebugger.py file be re-saved each time Sublime Text is re-opened

  #23 opened 11 years ago
  1

• file_type_list seems to randomly be set to None

  #22 opened 8 years ago
  1

• breakpoints are not visible in gutter when using gitgutter if there is already an icon for the line

  #21 opened 8 years ago
  0

• Add support for coffeescript

  #20 opened 8 years ago
  9

• Add to package control

  #19 opened 8 years ago
  2

• sublime text 2 - buffer is marked as dirty after save

  #18 opened 8 years ago
  0

• thoroughly comment source

  #17 opened 11 years ago
  1

• use a settings file instead of hardcoding settings

  #16 opened 11 years ago
  1

• add ability to save and load breakpoint sets

  #15 opened 8 years ago
  0

• if a line containing a breakpoint is removed entirely, that breakpoint should probably be removed

  #14 opened 8 years ago
  0

• if 2 breakpoints shift onto the same line, one can no longer be removed

  #13 opened 11 years ago
  1

• use is_visible() to enable/disable context commands

  #12 opened 8 years ago
  1

• use is_enabled() to enable/disable the plugin

  #11 opened 8 years ago
  0

• buffer is marked as dirty after save

  #10 opened 11 years ago
  0

• investigate using get_regions() to track breakpoint positions

  #9 opened 11 years ago
  1

• using undo after a save shows the debugger; statements

  #8 opened 8 years ago
  0

• adding a conditional breakpoint where a breakpoint already exists does not redraw the breakpoint icon to the correct color

  #7 opened 11 years ago
  0

• when a new/unnamed document is saved, the filename should be checked to see if it should be tracked

  #6 opened 11 years ago
  0

• SublimeText 2 errors

  #5 opened 11 years ago
  1

• When adding/removing lines in certain circumstances, breakpoints end up assigned to the wrong line or are removed entirely

  #4 opened 11 years ago
  1

• Error when trying to add a breakpoint

  #3 opened 11 years ago
  18

• Adding a breakpoint then using "undo", then trying to re-add the breakpoint throws an error

  #2 opened 11 years ago
  0

• Lines with "//" in a string are mistaken for comments, and the debugger statement is placed before the //

  #1 opened 11 years ago
  0