-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement jj next/prev #878
Comments
For now, you can add these aliases to your jj config to get something close: [alias]
prev = ["co", "@--"]
next = ["co", "@-+ ~ @"] but with a pretty big misfeature that in branch/merge cases instead of getting a picker to say which prev/next rev you want, it just blows up with an error about "more than one revision". |
I agree. FYI, @rslabbert talked (on Discord) about possibly implementing an interactive command for selecting a commit to check out or edit. Having |
Oh, another small usability improvement for "more than one revision": It wouldn't hurt anything to have the error list those actual multiple revisions it found, would it? Like:
|
It would probably not hurt anything to include up to, say, 5 commits there. If we wanted to format and color those commits as we usually, I'm not sure how to do it cleanly. So far, the errors we return have a single, plain-text error message, and an optional plain-text hint. We render the text in red and the hint in blue (by default). That happens here: Lines 1481 to 1487 in 4a889b9
It might be better to just render it as plain-text error plus hint then, pretty much as you suggested above:
|
Following the idea of #878 (comment), I like [revset-aliases]
next = "@-+ ~ @"
prev = "@--" # Though I usually just type @-- Then, you can do |
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes #878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes #878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I currently gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I gave each command separate a separate argument struct for extensibility. Fixes martinvonz#878
This is a naive implementation, which cannot deal with multiple children or parents stemming from merges. Note: I gave each command separate a separate argument struct for extensibility. Fixes #878
There should be a pair of commands
jj next
andjj prev
for quickly checking out the next/previous commit from@
, similar to the next/prev commands from git-branchless.The text was updated successfully, but these errors were encountered: