Deployed c2acc49 to prerelease with MkDocs 1.6.1 and mike 2.1.3

prerelease/config-schema.json

@@ -177,6 +177,16 @@
                     "type": "boolean",
                     "default": false,
                     "description": "Whether the built-in templates should show cryptographic signature information"
+                },
+                "movement": {
+                    "type": "object",
+                    "properties": {
+                        "edit": {
+                            "type": "boolean",
+                            "description": "Whether the next and prev commands should behave as if the --edit flag was passed",
+                            "default": false
+                        }
+                    }
                 }
             }
         },

prerelease/config/index.html

@@ -844,6 +844,15 @@
     </span>
   </a>
 
+</li>
+
+          <li class="md-nav__item">
+  <a href="#behavior-of-prev-and-next-commands" class="md-nav__link">
+    <span class="md-ellipsis">
+      Behavior of prev and next commands
+    </span>
+  </a>
+
 </li>
 
       </ul>
@@ -2193,6 +2202,15 @@
     </span>
   </a>
 
+</li>
+
+          <li class="md-nav__item">
+  <a href="#behavior-of-prev-and-next-commands" class="md-nav__link">
+    <span class="md-ellipsis">
+      Behavior of prev and next commands
+    </span>
+  </a>
+
 </li>
 
       </ul>
@@ -2996,6 +3014,17 @@ <h3 id="set-of-immutable-commits">Set of immutable commits<a class="headerlink"
 </code></pre></div>
 <p>Ancestors of the configured set are also immutable. The root commit is always
 immutable even if the set is empty.</p>
+<h3 id="behavior-of-prev-and-next-commands">Behavior of prev and next commands<a class="headerlink" href="#behavior-of-prev-and-next-commands" title="Permanent link">&para;</a></h3>
+<p>If you prefer using an "edit-based" workflow, rather than squashing
+modifications into parent changes, you may find yourself using the <code>prev</code> and
+<code>next</code> commands with their <code>--edit</code> flag often to move between your changes. You
+can avoid having to type the <code>--edit</code> flag every time you need it by actually
+making it the default:</p>
+<div class="highlight"><pre><span></span><code><span class="k">[ui.movement]</span>
+<span class="n">edit</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="kc">true</span>
+</code></pre></div>
+<p>You can pass the <code>--no-edit</code> flag to <code>prev</code> and <code>next</code> if you find yourself
+needing the original behavior.</p>
 <h2 id="log">Log<a class="headerlink" href="#log" title="Permanent link">&para;</a></h2>
 <h3 id="default-revisions">Default revisions<a class="headerlink" href="#default-revisions" title="Permanent link">&para;</a></h3>
 <p>You can configure the revisions <code>jj log</code> would show when neither <code>-r</code> nor any paths are specified.</p>