Replies: 1 comment 2 replies
|
The way you have stated it, it's not a subcommand, but a command. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm writing an alias that moves to a revision. I have 3 choices:
jj new -r <revision>-- always newjj edit -r <revision-- always editutil execand write a complicated bash script that picksjj neworjj edit, respecting--edit/--no-editandconfig.ui.movement.edit3 seems like the best option but it's cumbersome. If there was a
jj move-to -r <revision>command that handled respecting arguments and config for new vs. edit, my alias would become as simple as:And this would respect either using
neworeditbased onconfig.ui.movement.edit(and presumably could respect--edit/--no-editargs via pass-through?)You can think of this command as being analogous in behavior to
jj next/jj prev, in that all these commands would default tojj newsemantics while moving commits, but allow you to opt-in tojj editsemantics through either--editORconfig.ui.movement.edit = trueI haven’t given the name a lot of thought and would be happy with something else.
All reactions