From: Greg Hurrell Date: Fri, 08 May 2026 14:30:36 GMT Subject: Re: [PATCH] git-jump: pick a mode automatically when invoked without arguments Message-ID: In-Reply-To: <20260508141314.GB709299@coredump.intra.peff.net> 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...) > Would having "git jump auto" work for you? I.e., are you primarily > trying to avoid the mental effort of selecting the command, or the > finger effort of typing it? It's mostly the finger effort of typing it because I generally know exactly which mode I want; eg. - I'm in the middle of a rebase, and hit a conflict; 100% of the time, I want to explore the conflicts, so I want `git jump` to do `git jump merge`. - I have unstaged changes, and I want to make some tweaks before committing; so I want `git jump` to do `git jump diff`. - Otherwise, I'm wanting to search for something (ie. `git jump grep`), so by definition I'm going to be doing some extra typing anyway (ie. `git jump grep `). 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. [^1]: https://github.com/wincent/wincent/commit/99183f86fe35 [^2]: https://github.com/Homebrew/homebrew-core/commit/e9fc066240f2 Best wishes, Greg