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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@
8
8
9
9
* in the tiebreak module function tiebreak_on_visual has been added, to enable more coherent tie-breaking
10
10
11
+
* PopUpErrorAction has been added in order to inform the user in cases where to cannot parse the source code.
12
+
11
13
### Fixed
12
14
13
15
* fixed the empty brackets bug in the repair modulebugs with ":" addressed, needs more testing and a subsequent bug
@@ -52,6 +54,10 @@
52
54
53
55
* additionally, even in case of ties when tie-breaking on the lowest common ancestor, the visual proximity is now taken into account!
54
56
57
+
* in the partial module, the function partially_parse has been modified in order to accept one more optional Boolean parameter which when True causes the function to raise the initial syntax error it captured instead of returning None objects. By default the parameter is set to False.
58
+
59
+
* In the same spirit, the query module has been modified and has a new attribute in order to store the above exception. The application module checks if this attribute HUD stored exception and displays an error through the PopUpErrorAction!
Copy file name to clipboardExpand all lines: doc/SelectArgument.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,10 @@ But why both "above" and "up"? The difference lies in that above only counts "in
107
107
108
108

109
109
110
-
Please also pay attention to the fact that logical lines can extend over multiple "physical" lines. In such a case, as illustrated by the last example in the gif, physical lines still determine the line to which above/below refer and result and alternatives from that physical line will be prioritized, but alternatives will also be offered from the whole logical line! Other than that like case one.
110
+
Though if we want to be more precise, we count lines that contain the beginning of function calls! this is important because logical lines can extend over multiple "physical" lines. The last example in the gif contains such an example, physical lines still determine the line to which above/below refer and result and alternatives from that physical line will be prioritized, but alternatives will also be offered from the whole logical line!
0 commit comments