Deployed 62900c5 with MkDocs version: 1.5.2

common-workflows/force-manage-windows.html

@@ -1201,6 +1201,10 @@
         
       
         
+      
+        
+      
+        
       
         
       
@@ -1379,6 +1383,26 @@
   
   
   
+    <li class="md-nav__item">
+      <a href="../cli/global-state.html" class="md-nav__link">
+        
+  
+  <span class="md-ellipsis">
+    global-state
+  </span>
+  
+
+      </a>
+    </li>
+  
+
+              
+            
+              
+                
+  
+  
+  
     <li class="md-nav__item">
       <a href="../cli/visible-windows.html" class="md-nav__link">
         
@@ -2059,6 +2083,26 @@
   
   
   
+    <li class="md-nav__item">
+      <a href="../cli/move-to-monitor-workspace.html" class="md-nav__link">
+        
+  
+  <span class="md-ellipsis">
+    move-to-monitor-workspace
+  </span>
+  
+
+      </a>
+    </li>
+  
+
+              
+            
+              
+                
+  
+  
+  
     <li class="md-nav__item">
       <a href="../cli/focus-monitor.html" class="md-nav__link">
         
@@ -3992,7 +4036,7 @@
 
 <h1 id="force-manage-windows">Force Manage Windows</h1>
 <p>❗️<strong>NOTE</strong>: A significant number of force-manage window rules for the most
-common applications are <a href="https://github.com/LGUG2Z/komorebi/#generating-common-application-specific-configurations">already generated for
+common applications are <a href="https://github.com/LGUG2Z/komorebi-application-specific-configuration">already generated for
 you</a></p>
 <p>In some rare cases, a window may not automatically be registered to be managed
 by <code>komorebi</code>. You can add rules to enforce this behaviour in the