- 12 5月, 2017 1 次提交
-
-
由 Johannes Rieken 提交于
-
- 11 5月, 2017 33 次提交
-
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
由 isidor 提交于
fixes #8851
-
由 Johannes Rieken 提交于
This reverts commit f3ffc2ed.
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Johannes Rieken 提交于
-
由 Michel Kaporin 提交于
-
由 Johannes Rieken 提交于
-
由 Martin Aeschlimann 提交于
Lua syntax extension is missing 'goto' keyword
-
由 João Moreno 提交于
Correct LC_ALL. Resolves #26227
-
由 Johannes Rieken 提交于
-
由 Joao Moreno 提交于
-
由 Benjamin Pasero 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-
由 Andre Weinand 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
Fixes #26406 **Bug** If there is an active selection, the on Enter rules may use the wrong language mode which results in the incorrect `afterEnterText`. See #26406 for an example of this case **Fix** Use language mode from the selection and correctly compute offset when grabbing `afterEnterText`
-
由 Alex Dima 提交于
-
由 Anthony Sottile 提交于
-
由 Martin Aeschlimann 提交于
-
由 Matt Bierner 提交于
Fixes #26351 **bug** For the code ```js const x = <b>|</b>; ``` with the cursor at the `|`, on enter rules should change the code to: ```js const x = <b> | </b>; ``` However we currently do not handle this case. The cause is the extra semicolon at the end of the line. This causes `getEnterAction` to think we are in a javascript context for the onenter rules instead of in a js-tags context **fix** Pass in the column of the cursor when getting the language id to use for the on enter rules instead of using the end of the line. This ensures we are in the `jsx-tags` language in the above case
-
由 Alex Dima 提交于
-
由 rebornix 提交于
-
由 Alex Dima 提交于
-
由 Benjamin Pasero 提交于
-
由 Benjamin Pasero 提交于
-
- 10 5月, 2017 6 次提交
-
-
由 Alex Dima 提交于
-
由 Johannes Rieken 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Martin Aeschlimann 提交于
-
由 Ramya Achutha Rao 提交于
-