On Mon, Mar 5, 2018 at 2:08 AM, Ben Franksen wrote:
> I have just tried this and in fact when I resume the edit all the escape
> sequences are printed literally. However, the editor does react to them:
> I can quit using ":q" and the garbage on the screen isn't actually put
> in the log. Still a b
Am 05.03.2018 um 10:19 schrieb Ben Franksen:
> Am 05.03.2018 um 03:40 schrieb Evan Laforge:
>> Record changes in darcs 2.12.5, then say yes to "add a long comment"
>> where EDITOR=vim. Now ^Z out of vim, and then fg back. At that
>> point, vim is in command mode, but any keys just appear literall
On Mon, Mar 5, 2018 at 1:19 AM, Ben Franksen wrote:
> But you /can/ work in the same way with darcs: just don't (q)uit, rather
> say (d)one. Then use 'darcs amend' to add more changes or 'darcs amend
> --unrecord' to remove changes. There is also the --edit-long-comment
> option for amend.
Yes, I
Am 05.03.2018 um 01:47 schrieb Karl O. Pinc:
> On Sun, 4 Mar 2018 23:23:33 +0100
> Ben Franksen wrote:
>
>> What made me re-consider
>> the idea was that I found I like the way mercurial automatically
>> creates a branch when you pull a conflicting patch.
>
>> But
>> when you look at it from a d
Am 05.03.2018 um 03:40 schrieb Evan Laforge:
> On Sun, Mar 4, 2018 at 2:46 AM, Ben Franksen wrote:
>>> There are a few other quibbles, like how obliterate -O is too slow to
>>> be useful,
>>
>> (perhaps we should have made --no-minimize the default?)
>
> Is that what you get when you ^C while it'
