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
For quick query, we store (and show on demand) the exact entire query that was ran.
For ordinary queries, showing the text of the query might be confusing because the state of the libraries it depended on might have changed in the meantime.
For quick eval, there is nonetheless a piece of information that is relevant to show, but not so large that it is likely to confuse the user into thinking that that's all of the relevant information: the context of the token or line that quick eval was applied to. We could show this in the query history status line.
The text was updated successfully, but these errors were encountered:
We do show filename:startline but I agree the selected token would also be neat (in the case of predicate names, expressions might be too long to display).
For quick query, we store (and show on demand) the exact entire query that was ran.
For ordinary queries, showing the text of the query might be confusing because the state of the libraries it depended on might have changed in the meantime.
For quick eval, there is nonetheless a piece of information that is relevant to show, but not so large that it is likely to confuse the user into thinking that that's all of the relevant information: the context of the token or line that quick eval was applied to. We could show this in the query history status line.
The text was updated successfully, but these errors were encountered: