Re: [PATCH v3] git-jump: pick a mode automatically when invoked without arguments

From: Greg Hurrell <greg@hurrell.net>
Date: May 22, 2026, 07:33 UTC
Message-ID: <3c0edf5a-761a-4b79-bf3a-fcf336a986e8@app.fastmail.com>
In-Reply-To: <20260522052821.GC861761@coredump.intra.peff.net>

On Fri, May 22, 2026, at 7:28 AM, Jeff King wrote:

Show 7 quoted lines

> 
> My impression of the "auto" feature is: I am too lazy to type, so just
> take me to the interesting bits. And interesting in my experience with
> git-jump is either "I am merging, take me to the conflict" or "I am
> writing new code, take me to what I already did". Limiting the second
> case just to whitespace violations (assuming there is at least one)
> would probably be more confusing than helpful.

> If sounds like Greg has been living with "auto" and finding it useful
> for a while. So I'm mostly inclined to take the patch as-is, and people
> can experiment with it and suggest changes after using it in practice.

Yes, the "take me to the interesting bits" is very much the mental model I've been operating with, using the simplest definition of "interesting" ("merge conflicts", followed by "changes in the worktree"). I think that starting simple, but leaving the door open to possibly introducing more subtleties in the future makes the most sense.

- Greg