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
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
Since cgrep allows you to make queries using pattern files, the next logical step would be to have some way to bookmark common queries. This would require some new flag like --query=query-name. Behind the scenes I think this could just function the same way as the pattern files but instead of requiring the path they would just be stored in some common location by their query name.
Example
$ cgrep -q=latest-casks *.rb
There should also be some way to bookmark the previous query as well. (Usually you want to try the query first before deciding if it's worth saving.) Queries could also be imported from pattern files as well.
The text was updated successfully, but these errors were encountered:
The more I think about this the more I come to the conclusion that the simplest solution would just be to allow users to bookmark the previous query. A simple --save=query-name option should do the trick. This command would take precedence over all others.
Since cgrep allows you to make queries using pattern files, the next logical step would be to have some way to bookmark common queries. This would require some new flag like
--query=query-name
. Behind the scenes I think this could just function the same way as the pattern files but instead of requiring the path they would just be stored in some common location by their query name.Example
$ cgrep -q=latest-casks *.rb
There should also be some way to bookmark the previous query as well. (Usually you want to try the query first before deciding if it's worth saving.) Queries could also be imported from pattern files as well.
The text was updated successfully, but these errors were encountered: