Re: "Give me a break"... well, you gave me one

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Apr 1, 2019, 15:26 UTC
Message-ID: <nycvar.QRO.7.76.6.1904011724550.41@tvgsbejvaqbjf.bet>
In-Reply-To: <CAMPXz=qa5GA6zynpPWTDpKeh0J=p2y31xA7gwk5Y7swF2z1OHQ@mail.gmail.com>

Hi David,

On Sat, 30 Mar 2019, David wrote:

Show 10 quoted lines

> On Thu, 7 Mar 2019 at 09:00, Mike Hommey <mh@glandium.org> wrote:
> > On Wed, Mar 06, 2019 at 03:14:11PM +0100, Johannes Schindelin wrote:
> > >
> > > just wanted to express my gratitude for your idea to introduce the `break`
> > > command in `git rebase -i`'s todo list. I use it *all* the time now.
> >
> > +1. Before that, I was using `x bash`, and ended up doing `git rebase
> > --continue` in that shell in many cases, which didn't end up so well
>
> 'x bash' will start another shell, that seems an odd thing to do.

Indeed, but it used to work quite well for me, too. I usually made extra sure to start a new session by using `exec bash -i`...

> I have been using 'x false' to generate an error exit status to interrupt
> the rebase and drop into the current shell. Then 'git rebase --continue'
> to resume.

That's not so scriptable. I have a couple of scripts around the interactive rebase.

Besides, `b` is much shorter to type than `x false` (and I also cannot tyop it late at night as `x flase`, although that would have the same effect, I guess, of stopping the interactive rebase).

Ciao, Johannes