Re: How to extend a patch theory to fully commute

>> This suggests that we should present the "inactive" portions of a named
>> patch in a special way e.g. "shaded"or with a bit of extra markup. In
>> fact this may be superior to how Darcs operates today, where hitting 'v'
>> on a conflictor shows you its internal representation, which isn't too
>> helpful.
> 
> By hitting v do you mean passing -v to darcs changes? Or am I missing
> some cool Darcs UI?

Indeed! Try 'darcs log -i' (for interactive). For each patch you are
presentetd with a menu of keys to get more detailed information about
the patch. This is the same when you pull or push or whatever. Hitting
'?' will display help about the available keys.

Example:

>darcs log -i
patch a4b12fc212dadeacd92c47b262ff999db6451a69
Author: Ben Franksen <[email protected]>
Date:   Tue Nov  3 00:39:30 CET 2020
  * resolve issue2632: remove context from patch bundles

  The function makeBundle has one less parameter now and is pure.
Shall I view this patch? (1/?) [yN...], or ? for more options: ?
How to use view changes:
y: view this patch and go to the next
n: skip to the next patch

v: view this patch in full
p: view this patch in full with pager
r: view this patch
x: view a summary of this patch

q: quit view changes
k: back up to previous patch
j: skip to next patch
g: start over from the first patch
c: count total patch number

?: show this help

<Space>: accept the current default (which is capitalized)

Cheers
Ben