Thread (287 messages) 287 messages, 11 authors, 2018-10-08

Re: [PATCH 10/8] [DO NOT APPLY, but improve?] rebase--interactive: introduce "stop" command

From: Jacob Keller <hidden>
Date: 2018-01-18 22:10:19

On Thu, Jan 18, 2018 at 2:08 PM, Philip Oakley [off-list ref] wrote:
From: "Jacob Keller" <redacted>
quoted
On Thu, Jan 18, 2018 at 10:36 AM, Stefan Beller [off-list ref]
wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help