Re: [PATCH 10/8] [DO NOT APPLY, but improve?] rebase--interactive: introduce "stop" command
- From
Jacob Keller <jacob.keller@gmail.com>
- Date
- Jan 18, 2018, 22:09 UTC
- Message-ID
- <CA+P7+xpMGkBhBQEmB5akqi2hhCr=VzMbJopNPNbkAbF6sdzPUg@mail.gmail.com>
- In-Reply-To
- <32EA49C74ECD470F8EE898D965833E02@PhilipOakley>
On Thu, Jan 18, 2018 at 2:08 PM, Philip Oakley <philipoakley@iee.org> wrote:
Show 26 quoted lines
> From: "Jacob Keller" <jacob.keller@gmail.com> >> >> On Thu, Jan 18, 2018 at 10:36 AM, Stefan Beller <sbeller@google.com> >> wrote: >>> >>> Jake suggested using "x false" instead of "edit" for some corner cases. >>> >>> I do prefer using "x false" for all kinds of things such as stopping >>> before a commit (edit only let's you stop after a commit), and the >>> knowledge that "x false" does the least amount of actions behind my back. >>> >>> We should have that command as well, maybe? >>> >> >> >> I agree. I use "x false" very often, and I think stop is probably a >> better solution since it avoids spawning an extra shell that will just >> fail. Not sure if stop implies too much about "stop the whole thing" >> as opposed to "stop here and let me do something manual", but I think >> it's clear enough. >> > 'hold' or 'pause' maybe options (leads to > http://www.thesaurus.com/browse/put+on+hold offering procastinate etc.) > 'adjourn'. > >
I like break, as suggested by Dscho. That also works well for abbreviation if we drop the "bud" command.
Thanks, Jake