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: doc/README.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -547,20 +547,26 @@ Or we can paste them
547
547
548
548

549
549
550
-
Furthermore by using the prefix `operation` that appears at the start of selection queries
550
+
Furthermore by using the prefix `operation` that appears at the start of selection queries we can do that all in one go
551
+
552
+
But more on thought when we talk about [operations](./Operations.md)
551
553
552
554
553
555
### Collection Queries
554
556
555
-
Imagine a case where you have a variable or parameter name or an expression with perhaps many atoms that are hard to dictate.
557
+
but it can also collect all the modules function names and so on other in the file via [collection query](./CollectionQueries.md)
558
+
559
+

560
+
561
+
These would be displayed in a panel at the bottom of the screen and you can then insert one or more of them
556
562
557
-
If you dont want to rely on autocompletion you can for instance select it and paste it back:) But what if you need to write it several times in dofferent locations? Or what if it is so far away in the code you cannot really describe it?(say an imported item whose full name you dont even remember)
563
+

558
564
565
+
As it can become common that you have a variable or parameter name or an expression with perhaps many atoms that are hard to dictate, there is also one step approach for those
559
566
560
-
Collection Queries try to address this issue. These collect the text of interesting regions and display it on the bottom panel.
0 commit comments