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

From: Jeff King <peff@peff.net>
Date: May 8, 2026, 17:52 UTC
Message-ID: <20260508175240.GA737125@coredump.intra.peff.net>
In-Reply-To: <c5e0a1fa-f228-41dd-b547-07b0ad6c0964@app.fastmail.com>

On Fri, May 08, 2026 at 04:30:36PM +0200, Greg Hurrell wrote:

Show 10 quoted lines

> On Fri, May 8, 2026, at 4:13 PM, Jeff King wrote:
> > On Fri, May 08, 2026 at 09:07:34AM +0000, Greg Hurrell via GitGitGadget wrote:
> > 
> > I'd be a little worried that it is more confusing to somebody
> > approaching the command for the first time and just runs "git jump" to
> > not see usage or other guidance. But that might be overly paranoid.
> 
> Hopefully, they at least read the README before installing it from contrib/
> (although Homebrew recently starting installing it for folks automatically,
> so may not remain true for much longer on macOS...)

Yeah, I'd hope so. And even if it might be more discoverable, I'm not sure that is more important than being convenient for experienced users.

I guess a config option would be possible, but probably not worth it for something as trivial as git-jump.

> It's mostly the finger effort of typing it because I generally know exactly
> which mode I want; eg.

OK, that makes sense.

> This is muscle memory for me at this point, because I've had a `git jump`
> alias for this in my dotfiles[^1] for a couple of years. Homebrew
> installing `git-jump` by default a few months ago[^2] broke this, because
> aliases can't shadow builtin commands.

Ah, yeah, that is frustrating. We try to avoid aliases overrides to prevent confusion, but for an add-on tool like git-jump I think it is overly cautious. It might be reasonable to limit that protection only to commands in Git's exec-path, but I haven't thought hard about it. And I think it should be considered separately from this patch anyway.

So yeah, your patch looks good to me. Thanks.

-Peff