Skip to content

Commit db80070

Browse files
committed
Recommendation should be over
1 parent f87fcce commit db80070

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

doc/README.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -547,20 +547,26 @@ Or we can paste them
547547

548548
![](./gif/d2.gif)
549549

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)
551553

552554

553555
### Collection Queries
554556

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+
![](doc/gif/collect5.gif)
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
556562

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+
![](doc/gif/collect1.gif)
558564

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
559566

560-
Collection Queries try to address this issue. These collect the text of interesting regions and display it on the bottom panel.
561567

568+
![](doc/gif/collect6.gif)
562569

563-
![](./gif/d4.gif)
564570

565571

566572

0 commit comments

Comments
 (0)