##Impressions After Using It for a Week

I've been using komorebi on my work PC for a week. The good and bad points have become fairly clear, so I'll give an honest review. I hope this helps with choosing a window manager.

###Good Points

As expected, being able to arrange windows in tiles is really great. I sometimes code with VSCode + browser for research, and other times with VSCode + AI service¹. It's really good for keeping each screen configuration while quickly switching to Slack and then back.

When I want to do this kind of thing, I use the following keymaps:

1. First split VSCode and browser left and right (Screen 1)
2. Use Alt + Shift + 2 to move the VSCode screen and then open Poe.com (Screen 2)
3. Use Alt + Shift + 3 to move to Screen 3 where Slack is, then go back (Screen 3→2→1)

A pleasant surprise is that because window management has become easier, I've stopped utilizing multi-display. Until now, I kept Slack on the sub-display and worked on the main display, but now I can switch windows quickly with almost no eye movement. I don't want to think about it too much, but I'm starting to feel like I only need the ultrawide main display at home...

###Bad Points

One concern is that the behavior is unstable when connecting or disconnecting displays. I can accept the screen configuration changing, but sometimes a blank window occupies half the screen and can't be closed.

I often carry my laptop around at work. Basically, I connect to a display in my office for coding, and when there's a meeting, I take just the laptop to the meeting room or empty room and use it alone, or connect to the meeting room monitor. When changing connections frequently like this, I need to stop komorebi with Alt+p or restart it, which is quite tedious...

The stability changes when I modify komorebi.json settings, so it might purely be a bug issue.

Another concern is that windows that I don't want split are forcibly tile-arranged, so I need to pay attention when new windows pop up. However, this can be managed by editing applications.yaml to configure whether komorebi applies to each application. The creator has already set standard tools like Zoom and 1Password to be excluded from control, so if that's not enough, you can add more following those examples.

##Optimizing Settings

###Not Using the Bar

The bar feature is cool, but it only displays on one display with multi-display, and it doesn't sync with hotkey screen switching, so I decided not to use it.

Just don't add the --bar option when starting.

komorebic start --whkd

###applications.yaml

As mentioned above, I've only registered Arc browser's picture in picture in applications.yaml.

You can find the current window name/ID name by running the komorebic state command while komorebi is running and the screen is open.

- name: pip
  identifier:
    kind: Exe
    id: Arc.exe
    matching_strategy: Equals
  float_identifiers:
  - kind: Title
    id: Arc picture in picture
    matching_strategy: Equals

###komorebi.json

In the end, I don't use the bar feature so there's no need to adjust offset, and I settled on just tweaking the padding width a bit.

{
  "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.29/schema.json",
  "app_specific_configuration_path": "$Env:KOMOREBI_CONFIG_HOME/applications.yaml",
  "window_hiding_behaviour": "Cloak",
  "cross_monitor_move_behaviour": "Insert",
  "default_workspace_padding": 2,
  "default_container_padding": 2,
  "border": true,
  "border_width": 8,
  "border_offset": -1,
  "theme": {
    "palette": "Base16",
    "name": "Helios",
    "unfocused_border": "Base03",
    "bar_accent": "Base0D"
  },
  "stackbar": {
    "height": 30,
    "mode": "OnStack",
    "tabs": {
      "width": 300
    }
  },
  "focus_follows_mouse": "Komorebi",
  "transparency": true,
  "transparency_alpha": 250,
  "monitors": [
    {
      "workspaces": [
        {
          "name": "I",
          "layout": "BSP"
        },
        {
          "name": "II",
          "layout": "BSP"
        },
        {
          "name": "III",
          "layout": "BSP"
        },
        {
          "name": "IV",
          "layout": "BSP"
        },
        {
          "name": "V",
          "layout": "BSP"
        },
        {
          "name": "VI",
          "layout": "BSP"
        },
        {
          "name": "VII",
          "layout": "BSP"
        }
      ]
    }
  ]
}