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
Playing with the new query builder: such a powerful tool. It's clear you spent a long while getting the interface just right.
A few things I noticed:
I don't know how to quit the query-builder. Just kill the buffer? A q binding on the transient would be nice to quit and clean-up (and maybe prompt to save the query on the query ring).
As you experiment, often the positive results of older queries are not erased. I.e. highlighting remains.
The completion of types is simply wonderful. Field names for given types also work, but not based on the text in-buffer. I.e. in (dictionary (pair [X]) @hl.silver), with point after the pair , M-Tab gives a list of fields, but entering a fragment of one and completing ((dictionary (pair ke[X]) @hl.silver)) does not.
Would be great if @before/@after etc. were presented as capturing completions, in addition to the highlight colors.
A binding for M-g p/n to move to the previous/next known error position (if any) would be lovely.
Just started playing; thanks again for this powerful tool.
The text was updated successfully, but these errors were encountered:
Playing with the new query builder: such a powerful tool. It's clear you spent a long while getting the interface just right.
A few things I noticed:
q
binding on the transient would be nice to quit and clean-up (and maybe prompt to save the query on the query ring).(dictionary (pair [X]) @hl.silver)
, with point after thepair
,M-Tab
gives a list of fields, but entering a fragment of one and completing((dictionary (pair ke[X]) @hl.silver)
) does not.@before
/@after
etc. were presented as capturing completions, in addition to the highlight colors.M-g p/n
to move to the previous/next known error position (if any) would be lovely.Just started playing; thanks again for this powerful tool.
The text was updated successfully, but these errors were encountered: