YaLTeR / niri

A scrollable-tiling Wayland compositor.
https://matrix.to/#/#niri:matrix.org
GNU General Public License v3.0
4.12k stars 123 forks source link

Named workspaces no longer appear in the order they are defined in. #706

Closed blackdragon2447 closed 1 month ago

blackdragon2447 commented 1 month ago

Since 0.1.9, name workspaces do no longer appear in the order they are defined in, now seemingly appearing in a random order. New (unnamed) workspaces being created will cause this order to be reshuffled, with the unnamed workspaces appearing somewhere between the named ones. The order is different every startup.

System Information

YaLTeR commented 1 month ago

Could you show your niri config.kdl? Also if you run nested niri in a window then inside run niri msg workspaces, is it also inconsistent every startup?

blackdragon2447 commented 1 month ago
input {
    keyboard {
        xkb {
            layout ""
            model ""
            rules ""
            variant ""
            options "caps:menu"
        }
        repeat-delay 600
        repeat-rate 25
        track-layout "global"
    }
    touchpad {
        tap
        natural-scroll
        accel-speed 0.000000
        click-method "clickfinger"
        tap-button-map "left-right-middle"
    }
    mouse { accel-speed 0.000000; }
    trackpoint { accel-speed 0.000000; }
    tablet
    touch
    focus-follows-mouse
}

output "eDP-1" {
    scale 1
    transform "normal"
}

screenshot-path "~/Pictures/Screenshots/Screenshot from %Y-%m-%d %H-%M-%S.png"

prefer-no-csd

layout {
    gaps 16
    struts {
        left 0
        right 0
        top 0
        bottom 0
    }
    focus-ring {
        width 2
        active-color "#f04339"
        inactive-color "#22262d"
    }
    border { off; }
    default-column-width
    center-focused-column "never"
}

cursor {
    xcursor-theme "default"
    xcursor-size 12
}

hotkey-overlay
environment {
    "ELECTRON_OZONE_PLATFORM_HINT" "auto"
    "MOZ_ENABLE_WAYLAND" "1"
    "_JAVA_AWT_WM_NONREPARENTING" "1"
}
binds {
    // snip
}

// Worlspaces here
workspace " "
workspace "󰈹 "
workspace " "
workspace " "

spawn-at-startup "/nix/store/wxkxcrd3vlgjpgma9xffsysmnnsjf4fd-cage-0.1.5-unstable-2024-07-29/bin/cage" "Discord"
spawn-at-startup "cinny"
spawn-at-startup "firefox"
spawn-at-startup "thunderbird"
spawn-at-startup "waybar"

window-rule {
    match app-id="firefox"
    open-on-workspace "01-browser"
}
window-rule {
    match title=".*Discord"
    match app-id="cinny"
    match app-id=".*nheko.*"
    open-on-workspace "chat"
}
window-rule {
    match app-id="thunderbird"
    open-on-workspace "03-mail"
}

animations { slowdown 1.000000; }

niri msg workspaces is correct in a nested session, niri msg -j workspaces is not however.

Edit: format config

YaLTeR commented 1 month ago

niri msg -j workspaces ordering is undefined. They all have an index field that is the number you're looking for (index of that workspace on its output).

blackdragon2447 commented 1 month ago

Ah, that explains, it seemed (intentional or not) consistent in past versions. Anyway, thank you, that fixes my issue.