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 May 17, 2018. It is now read-only.
I often clk in to work on items where the default format for specifying tags and the message is redundant. For instance, when reviewing a changeset for one client, I naturally copy text like foo-selenium#e1234 into the copy buffer. I then immediately do
clk in .client .foo .review foo-selenium#e1234
with my old clk program, I could do
clk in review foo-selenium#e1234
which expanded to something like the first example.
It would be convenient if there were a "pre-in" hook which received all the clk in command line arguments as command line arguments. It would print a list of command line arguments to STDOUT which clk would use as its actual command line arguments.
This same mechanism could be used for catching typos too. If the pre-in script exited with an error code, the clk in would halt and the hook's STDERR would be displayed to the user.
The text was updated successfully, but these errors were encountered:
I often clk in to work on items where the default format for specifying tags and the message is redundant. For instance, when reviewing a changeset for one client, I naturally copy text like
foo-selenium#e1234
into the copy buffer. I then immediately dowith my old clk program, I could do
which expanded to something like the first example.
It would be convenient if there were a "pre-in" hook which received all the
clk in
command line arguments as command line arguments. It would print a list of command line arguments to STDOUT whichclk
would use as its actual command line arguments.This same mechanism could be used for catching typos too. If the pre-in script exited with an error code, the
clk in
would halt and the hook's STDERR would be displayed to the user.The text was updated successfully, but these errors were encountered: