You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
exportconsteditorBracketMatchBorder=registerColor('editorBracketMatch.border',{dark: '#888',light: '#B9B9B9',hc: contrastBorder},nls.localize('editorBracketMatchBorder','Color for matching brackets boxes'));
37
37
38
38
exportconsteditorOverviewRulerBorder=registerColor('editorOverviewRuler.border',{dark: '#7f7f7f4d',light: '#7f7f7f4d',hc: '#7f7f7f4d'},nls.localize('editorOverviewRulerBorder','Color of the overview ruler border.'));
39
+
exportconsteditorOverviewRulerBackground=registerColor('editorOverviewRuler.background',null,nls.localize('editorOverviewRulerBackground','Background color of the editor overview ruler. Only used when the minimap is enabled and placed on the right side of the editor.'));
39
40
40
41
exportconsteditorGutter=registerColor('editorGutter.background',{dark: editorBackground,light: editorBackground,hc: editorBackground},nls.localize('editorGutter','Background color of the editor gutter. The gutter contains the glyph margins and the line numbers.'));
* VS Code can call the `provideDebugConfigurations` method of a `DebugConfigurationProvider` in two situations (aka 'scopes'):
724
-
* to provide the initial debug configurations for a newly created launch.json or to provide debug configurations dynamically based on context.
725
-
* A scope can be used when registering a `DebugConfigurationProvider` with #debug.registerDebugConfigurationProvider.
723
+
* A DebugConfigurationProviderTrigger specifies when the `provideDebugConfigurations` method of a `DebugConfigurationProvider` is triggered.
724
+
* Currently there are two situations: to provide the initial debug configurations for a newly created launch.json or
725
+
* to provide dynamically generated debug configurations when the user asks for them through the UI (e.g. via the "Select and Start Debugging" command).
726
+
* A trigger is used when registering a `DebugConfigurationProvider` with #debug.registerDebugConfigurationProvider.
726
727
*/
727
-
exportenumDebugConfigurationProviderScope{
728
+
exportenumDebugConfigurationProviderTrigger{
728
729
/**
729
-
* The 'initial' scope is used to ask for debug configurations to be copied into a newly created launch.json.
730
+
* `DebugConfigurationProvider.provideDebugConfigurations` is called to provide the initial debug configurations for a newly created launch.json.
730
731
*/
731
732
Initial=1,
732
733
/**
733
-
* The 'dynamic' scope is used to ask for additional dynamic debug configurations to be presented to the user (in addition to the static configurations from the launch.json).
734
+
* `DebugConfigurationProvider.provideDebugConfigurations` is called to provide dynamically generated debug configurations when the user asks for them through the UI (e.g. via the "Select and Start Debugging" command).
734
735
*/
735
736
Dynamic=2
736
737
}
737
738
738
739
exportnamespacedebug{
739
740
/**
740
741
* Register a [debug configuration provider](#DebugConfigurationProvider) for a specific debug type.
741
-
* The optional [scope](#DebugConfigurationProviderScope) argument can be used to bind the `provideDebugConfigurations` method of the provider to a specific context (aka scope).
742
-
* Currently two scopes are possible: with the value `Initial` (or if no scope argument is given) the `provideDebugConfigurations` method is used to find the initial debug configurations to be copied into a newly created launch.json.
743
-
* With a scope value `Dynamic` the `provideDebugConfigurations` method is used to dynamically determine debug configurations to be presented to the user in addition to the static configurations from the launch.json.
744
-
* Please note that the scope argument only applies to the `provideDebugConfigurations` method: so the `resolveDebugConfiguration` methods are not affected at all.
745
-
* Registering a single provider with resolve methods for different scopes, results in the same resolve methods called multiple times.
742
+
* The optional [trigger](#DebugConfigurationProviderTrigger) can be used to specify when the `provideDebugConfigurations` method of the provider is triggered.
743
+
* Currently two triggers are possible: with the value `Initial` (or if no trigger argument is given) the `provideDebugConfigurations` method is used to provide the initial debug configurations to be copied into a newly created launch.json.
744
+
* With the trigger `Dynamic` the `provideDebugConfigurations` method is used to dynamically determine debug configurations to be presented to the user (in addition to the static configurations from the launch.json).
745
+
* Please note that the `trigger` argument only applies to the `provideDebugConfigurations` method: so the `resolveDebugConfiguration` methods are not affected at all.
746
+
* Registering a single provider with resolve methods for different triggers, results in the same resolve methods called multiple times.
746
747
* More than one provider can be registered for the same type.
747
748
*
748
749
* @param type The debug type for which the provider is registered.
749
750
* @param provider The [debug configuration provider](#DebugConfigurationProvider) to register.
750
-
* @paramscope The [scope](#DebugConfigurationProviderScope) for which the 'provideDebugConfiguration' method of the provider is registered.
751
+
* @paramtrigger The [trigger](#DebugConfigurationProviderTrigger) for which the 'provideDebugConfiguration' method of the provider is registered.
751
752
* @return A [disposable](#Disposable) that unregisters this provider when being disposed.
0 commit comments