- 27 3月, 2020 1 次提交
-
-
由 Alex Dima 提交于
-
- 26 3月, 2020 1 次提交
-
-
由 Alex Dima 提交于
-
- 20 3月, 2020 1 次提交
-
-
由 Alex Dima 提交于
-
- 18 3月, 2020 1 次提交
-
-
由 Alex Dima 提交于
-
- 05 3月, 2020 3 次提交
-
-
由 Alex Dima 提交于
-
由 Martin Aeschlimann 提交于
-
由 Martin Aeschlimann 提交于
-
- 26 2月, 2020 1 次提交
-
-
由 rebornix 提交于
-
- 22 2月, 2020 2 次提交
- 21 2月, 2020 1 次提交
-
-
由 Alex Dima 提交于
-
- 19 2月, 2020 2 次提交
-
-
由 Alex Dima 提交于
-
由 bolinfest 提交于
With the upcoming changes in TypeScript 3.8 to support `import type`, it is even more compelling to declare weak references via types rather than strong references via concrete classes. Most APIs in Monaco already do this well, accepting `monaco.IRange` instead of `monaco.Range`, though `IIdentifiedSingleEditOperation` appears to be an exception in this regard, which means a strong dependency on `monaco.Range` is required to use `ITextModel.pushEditOperations()`. It would be nice to relax this constraint, though I admit I have not yet attempted to trace through whether this breaks anything since I am submitting this via GitHub's web UI.
-
- 05 2月, 2020 1 次提交
-
-
由 Alex Dima 提交于
-
- 11 12月, 2019 1 次提交
-
-
由 Alexandru Dima 提交于
-
- 06 12月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 07 11月, 2019 1 次提交
-
-
由 Alexandru Dima 提交于
-
- 06 11月, 2019 2 次提交
-
-
由 Rachel Macfarlane 提交于
-
由 Alexandru Dima 提交于
-
- 26 10月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 18 10月, 2019 1 次提交
-
-
由 Alexandru Dima 提交于
-
- 17 10月, 2019 2 次提交
-
-
由 Alexandru Dima 提交于
-
由 Alex Dima 提交于
-
- 19 7月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 10 7月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 09 7月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 21 6月, 2019 1 次提交
-
-
由 Rachel Macfarlane 提交于
-
- 16 4月, 2019 1 次提交
-
-
由 Benjamin Pasero 提交于
-
- 06 3月, 2019 1 次提交
-
-
由 Matt Bierner 提交于
-
- 28 2月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 27 2月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 18 2月, 2019 2 次提交
-
-
由 Alex Dima 提交于
-
由 David Lechner 提交于
This is an attempt to address issue #10339. Background: Currently, the `editor.tabSize` option does two things - it specifies the width of the tab character and it specifies how many columns to advance when the tab key is pressed. However, there is code in the wild that has a mix of spaces and tabs that expects these two values to be different. These generally use and indent size of 2 or 4 and spaces are used for indentation until the indent becomes >= 8. The tab character size is excpected to be 8 and groups of 8 spaces are replaced with a tab character. Indent levels end up looking like 2 spaces, 4 spaces, 6 spaces, 1 tab, 1 tab + 2 spaces, and so on. Implementation: In the editor options, a new option, `editor.indentSize` is added. This, in conjunction with `editor.tabSize` has the same semantics as `indent_size` and `tab_width` in the well known [EditorConfig specification][1]. > indent_size: a whole number defining the number of columns used for each indentation level and the width of soft tabs (when supported). When set to "tab", the value of tab_width (if specified) will be used. > > tab_width: a whole number defining the number of columns used to represent a tab character. This defaults to the value of indent_size and doesn't usually need to be specified. [1]: editorconfig.org The new `indentSize` option takes a numeric value or "tab" just as EditorConfig's `indent_size`. The default value is set to "tab" so that current default behavior of VS Code does not change and existing user settings will not break. When getting the new `indentSize` option programatically, it always returns a numeric value (just as `tabSize` does when set to the deprecated "auto" value). In the text editor model, a new property is added for `indentSize`. Unlike the configuration options where the value of one property influences the other, In this code `tabSize` now should only mean "the width of the tab character" and `indentSize` should only mean "how may columns is one indent". The cursor operations and shift command are updated to reflect these new semantics.
-
- 18 1月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 31 10月, 2018 1 次提交
-
-
由 Alex Dima 提交于
-
- 23 10月, 2018 1 次提交
-
-
由 Alex Dima 提交于
-
- 22 10月, 2018 1 次提交
-
-
由 Alex Dima 提交于
-
- 13 10月, 2018 1 次提交
-
-
由 Alex Dima 提交于
-
- 12 10月, 2018 2 次提交