Cleaning up the plugin a bit, seems like going the build system route was not worth it. Minimal gains, a lot of additional mental overhead. As much as I love sublime the plugin api is not great for more complicated things. Instead by default plugin seeks for a nearby remedy file, hopefully this will help a bit.
38 lines
860 B
Plaintext
38 lines
860 B
Plaintext
[
|
|
{
|
|
"caption": "RemedyBG: Launch",
|
|
"command": "remedy_launch",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Goto to cursor in remedy",
|
|
"command": "remedy_go_to_cursor",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Start debugging",
|
|
"command": "remedy_start_debugging",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Stop debugging",
|
|
"command": "remedy_stop_debugging",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Set breakpoint",
|
|
"command": "remedy_set_breakpoint",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Set conditional breakpoint",
|
|
"command": "remedy_set_conditional_breakpoint",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Run to cursor, launch and stop at cursor",
|
|
"command": "remedy_run_to_cursor",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Restart debugging",
|
|
"command": "remedy_restart_debugging",
|
|
},
|
|
{
|
|
"caption": "RemedyBG: Add selection or word under cursor to watch window",
|
|
"command": "remedy_add_to_watch",
|
|
},
|
|
] |