diff options
| -rw-r--r-- | dot-config/niri/config.kdl | 548 |
1 files changed, 161 insertions, 387 deletions
diff --git a/dot-config/niri/config.kdl b/dot-config/niri/config.kdl index 3ba9866..c985a81 100644 --- a/dot-config/niri/config.kdl +++ b/dot-config/niri/config.kdl @@ -1,301 +1,134 @@ -// This config is in the KDL format: https://kdl.dev -// "/-" comments out the following node. -// Check the wiki for a full description of the configuration: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Introduction - -// Input device configuration. -// Find the full list of options on the wiki: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Input +// +// NIRI CONFIG +// For more info see: https://github.com/YaLTeR/niri/wiki/ + +cursor { + hide-when-typing + //hide-after-inactive-ms 3000 + xcursor-theme "Adwaita" + //xcursor-size 32 +} + +overview { + //zoom 0.25 +} + +hotkey-overlay { + skip-at-startup +} + input { keyboard { xkb { - // You can set rules, model, layout, variant and options. - // For more information, see xkeyboard-config(7). - - // For example: layout "gb" options "ctrl:nocaps" + //options "ctrl:swapcaps" } - - // Enable numlock on startup, omitting this setting disables it. - numlock } - - // Next sections include libinput settings. - // Omitting settings disables them, or leaves them at their default values. touchpad { - // off tap - // dwt - // dwtp - // drag false - // drag-lock - natural-scroll - // accel-speed 0.2 - // accel-profile "flat" - // scroll-method "two-finger" - // disabled-on-external-mouse + dwt + middle-emulation + //natural-scroll } - mouse { - // off - // natural-scroll - // accel-speed 0.2 - // accel-profile "flat" - // scroll-method "no-scroll" - } - - trackpoint { - // off - // natural-scroll - // accel-speed 0.2 - // accel-profile "flat" - // scroll-method "on-button-down" - // scroll-button 273 - // middle-emulation - } - - // Uncomment this to make the mouse warp to the center of newly focused windows. - // warp-mouse-to-focus + warp-mouse-to-focus +} - // Focus windows and outputs automatically when moving the mouse into them. - // Setting max-scroll-amount="0%" makes it work only on windows already fully on screen. - // focus-follows-mouse max-scroll-amount="0%" +// Laptop +output "eDP-1" { + mode "2944x1849@60" + scale 2 } -// You can configure outputs by their name, which you can find -// by running `niri msg outputs` while inside a niri instance. -// The built-in laptop monitor is usually called "eDP-1". -// Find more information on the wiki: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Outputs -// Remember to uncomment the node by removing "/-"! +// PC Monitor 1 output "DP-3" { - // Uncomment this line to disable this output. - // off - - // Resolution and, optionally, refresh rate of the output. - // The format is "<width>x<height>" or "<width>x<height>@<refresh rate>". - // If the refresh rate is omitted, niri will pick the highest refresh rate - // for the resolution. - // If the mode is omitted altogether or is invalid, niri will pick one automatically. - // Run `niri msg outputs` while inside a niri instance to list all outputs and their modes. mode "3840x2160@60" - - // You can use integer or fractional scale, for example use 1.5 for 150% scale. scale 1 - - // Transform allows to rotate the output counter-clockwise, valid values are: - // normal, 90, 180, 270, flipped, flipped-90, flipped-180 and flipped-270. transform "normal" - - // Position of the output in the global coordinate space. - // This affects directional monitor actions like "focus-monitor-left", and cursor movement. - // The cursor can only move between directly adjacent outputs. - // Output scale and rotation has to be taken into account for positioning: - // outputs are sized in logical, or scaled, pixels. - // For example, a 3840×2160 output with scale 2.0 will have a logical size of 1920×1080, - // so to put another output directly adjacent to it on the right, set its x to 1920. - // If the position is unset or results in an overlap, the output is instead placed - // automatically. position x=1280 y=0 + focus-at-startup } -// You can configure outputs by their name, which you can find -// by running `niri msg outputs` while inside a niri instance. -// The built-in laptop monitor is usually called "eDP-1". -// Find more information on the wiki: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Outputs -// Remember to uncomment the node by removing "/-"! +// PC Monitor 2 output "HDMI-A-5" { - // Uncomment this line to disable this output. - // off - - // Resolution and, optionally, refresh rate of the output. - // The format is "<width>x<height>" or "<width>x<height>@<refresh rate>". - // If the refresh rate is omitted, niri will pick the highest refresh rate - // for the resolution. - // If the mode is omitted altogether or is invalid, niri will pick one automatically. - // Run `niri msg outputs` while inside a niri instance to list all outputs and their modes. mode "1920x1200@60" - - // You can use integer or fractional scale, for example use 1.5 for 150% scale. scale 1 - - // Transform allows to rotate the output counter-clockwise, valid values are: - // normal, 90, 180, 270, flipped, flipped-90, flipped-180 and flipped-270. transform "90" - - // Position of the output in the global coordinate space. - // This affects directional monitor actions like "focus-monitor-left", and cursor movement. - // The cursor can only move between directly adjacent outputs. - // Output scale and rotation has to be taken into account for positioning: - // outputs are sized in logical, or scaled, pixels. - // For example, a 3840×2160 output with scale 2.0 will have a logical size of 1920×1080, - // so to put another output directly adjacent to it on the right, set its x to 1920. - // If the position is unset or results in an overlap, the output is instead placed - // automatically. position x=1280 y=0 } -// Settings that influence how windows are positioned and sized. -// Find more information on the wiki: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Layout layout { - // Set gaps around windows in logical pixels. - gaps 80 + center-focused-column "never" + always-center-single-column - // When to center a column when changing focus, options are: - // - "never", default behavior, focusing an off-screen column will keep at the left - // or right edge of the screen. - // - "always", the focused column will always be centered. - // - "on-overflow", focusing a column will center it if it doesn't fit - // together with the previously focused column. - center-focused-column "on-overflow" + gaps 80 - always-center-single-column + struts { + // left 64 + // right 64 + // top 64 + // bottom 64 + } - // You can customize the widths that "switch-preset-column-width" (Mod+R) toggles between. + // Width proportions preset-column-widths { - // Proportion sets the width as a fraction of the output width, taking gaps into account. - // For example, you can perfectly fit four windows sized "proportion 0.25" on an output. - // The default preset widths are 1/3, 1/2 and 2/3 of the output. - proportion 0.33333 proportion 0.5 - proportion 0.66667 - - // Fixed sets the width in logical pixels exactly. - // fixed 1920 + proportion 0.6 + proportion 0.8 } - // You can also customize the heights that "switch-preset-window-height" (Mod+Shift+R) toggles between. - // preset-window-heights { } + // Height proportions + preset-window-heights { + proportion 0.5 + proportion 0.6 + proportion 0.8 + } - // You can change the default width of the new windows. + // Default new window proportion default-column-width { proportion 0.5; } - // If you leave the brackets empty, the windows themselves will decide their initial width. - // default-column-width {} - - // By default focus ring and border are rendered as a solid background rectangle - // behind windows. That is, they will show up through semitransparent windows. - // This is because windows using client-side decorations can have an arbitrary shape. - // - // If you don't like that, you should uncomment `prefer-no-csd` below. - // Niri will draw focus ring and border *around* windows that agree to omit their - // client-side decorations. - // - // Alternatively, you can override it with a window rule called - // `draw-border-with-background`. - // You can change how the focus ring looks. focus-ring { - // Uncomment this line to disable the focus ring. - //off - - // How many logical pixels the ring extends out from the windows. + off width 4 - // Colors can be set in a variety of ways: - // - CSS named colors: "red" - // - RGB hex: "#rgb", "#rgba", "#rrggbb", "#rrggbbaa" - // - CSS-like notation: "rgb(255, 127, 0)", rgba(), hsl() and a few others. - - // Color of the ring on the active monitor. active-color "#7fc8ff" - - // Color of the ring on inactive monitors. inactive-color "#505050" - // You can also use gradients. They take precedence over solid colors. - // Gradients are rendered the same as CSS linear-gradient(angle, from, to). - // The angle is the same as in linear-gradient, and is optional, - // defaulting to 180 (top-to-bottom gradient). - // You can use any CSS linear-gradient tool on the web to set these up. - // Changing the color space is also supported, check the wiki for more info. - // - active-gradient from="purple" to="cyan" angle=45 - - // You can also color the gradient relative to the entire view - // of the workspace, rather than relative to just the window itself. - // To do that, set relative-to="workspace-view". - // - // inactive-gradient from="5050" to="#808080" angle=45 relative-to="workspace-view" - // off + active-gradient from="purple" to="cyan" angle=45 relative-to="workspace-view" + inactive-gradient from="5050" to="#808080" angle=45 relative-to="workspace-view" } - // You can also add a border. It's similar to the focus ring, but always visible. border { - // The settings are the same as for the focus ring. - // If you enable the border, you probably want to disable the focus ring. - off - width 4 + active-color "#ffc87f" inactive-color "#505050" - // Color of the border around windows that request your attention. - urgent-color "#9b0000" + active-gradient from="purple" to="cyan" angle=45 + inactive-gradient from="5050" to="#808080" angle=45 relative-to="workspace-view" - // active-gradient from="#ffbb66" to="#ffc880" angle=45 relative-to="workspace-view" - // inactive-gradient from="#505050" to="#808080" angle=45 relative-to="workspace-view" + urgent-color "#9b0000" } - // You can enable drop shadows for windows. shadow { - // Uncomment the next line to enable shadows. on - - // By default, the shadow draws only around its window, and not behind it. - // Uncomment this setting to make the shadow draw behind its window. - // - // Note that niri has no way of knowing about the CSD window corner - // radius. It has to assume that windows have square corners, leading to - // shadow artifacts inside the CSD rounded corners. This setting fixes - // those artifacts. - // - // However, instead you may want to set prefer-no-csd and/or - // geometry-corner-radius. Then, niri will know the corner radius and - // draw the shadow correctly, without having to draw it behind the - // window. These will also remove client-side shadows if the window - // draws any. - // - // draw-behind-window true - - // You can change how shadows look. The values below are in logical - // pixels and match the CSS box-shadow properties. - - // Softness controls the shadow blur radius. + color "#0007" softness 30 - - // Spread expands the shadow. spread 5 - - // Offset moves the shadow relative to the window. offset x=0 y=5 - - // You can also change the shadow color and opacity. - color "#0007" - } - - // Struts shrink the area occupied by windows, similarly to layer-shell panels. - // You can think of them as a kind of outer gaps. They are set in logical pixels. - // Left and right struts will cause the next window to the side to always be visible. - // Top and bottom struts will simply add outer gaps in addition to the area occupied by - // layer-shell panels and regular gaps. - struts { - left 64 - right 64 - // top 64 - // bottom 64 } } -// Add lines like this to spawn processes at startup. -// Note that running niri as a session supports xdg-desktop-autostart, -// which may be more convenient to use. -// See the binds section below for more spawn examples. - -spawn-at-startup "ironbar" -spawn-at-startup "swww-daemon" +// PROCESSES +spawn-at-startup "mako" +spawn-at-startup "waybar" +spawn-at-startup "foot" "--server" +spawn-at-startup "pipewire" +spawn-at-startup "pipewire-pulse" +spawn-at-startup "wireplumber" +spawn-at-startup "swaybg" "-i" "/home/blake/.cache/wallpaper" +spawn-at-startup "wlsunset" "-l" "51.5" "-L" "0.1" "-t" "2800" "-T" "6000" // Uncomment this line to ask the clients to omit their client-side decorations if possible. // If the client will specifically ask for CSD, the request will be honored. @@ -304,105 +137,74 @@ spawn-at-startup "swww-daemon" // After enabling or disabling this, you need to restart the apps for this to take effect. prefer-no-csd -// You can change the path where screenshots are saved. // A ~ at the front will be expanded to the home directory. // The path is formatted with strftime(3) to give you the screenshot date and time. -screenshot-path "~/Pictures/Screenshots/Screenshot from %Y-%m-%d %H-%M-%S.png" +screenshot-path "~/images/screenshots/%F_%T.png" -// You can also set this to null to disable saving screenshots to disk. -// screenshot-path null -// Animation settings. -// The wiki explains how to configure individual animations: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Animations animations { // Uncomment to turn off all animations. // off - // Slow down all animations by this factor. Values below 1 speed them up instead. + // Slow down all animations by this factor. + // Values below 1 speed them up instead. slowdown 2.0 } -// Window rules let you adjust behavior for individual windows. -// Find more information on the wiki: -// https://github.com/YaLTeR/niri/wiki/Configuration:-Window-Rules +// +// WINDOW RULES +// -// Work around WezTerm's initial configure bug -// by setting an empty default-column-width. +// Default window-rule { - // This regular expression is intentionally made as specific as possible, - // since this is the default config, and we want no false positives. - // You can get away with just app-id="wezterm" if you want. - match app-id=r#"^org\.wezfurlong\.wezterm$"# - default-column-width {} + geometry-corner-radius 8 + clip-to-geometry true } -// Open the Firefox picture-in-picture player as floating by default. window-rule { - // This app-id regular expression will work for both: - // - host Firefox (app-id is "firefox") - // - Flatpak Firefox (app-id is "org.mozilla.firefox") - match app-id=r#"firefox$"# title="^Picture-in-Picture$" - open-floating true + match app-id="librewolf" + open-maximized false } -// Example: block out two password managers from screen capture. -// (This example rule is commented out with a "/-" in front.) -/-window-rule { - match app-id=r#"^org\.keepassxc\.KeePassXC$"# - match app-id=r#"^org\.gnome\.World\.Secrets$"# - - block-out-from "screen-capture" - - // Use this instead if you want them visible on third-party screenshot tools. - // block-out-from "screencast" +window-rule { + match app-id="librewolf" title="^Picture-in-Picture$" + open-floating true } -// Example: enable rounded corners for all windows. -// (This example rule is commented out with a "/-" in front.) window-rule { - geometry-corner-radius 8 - clip-to-geometry true + match app-id="swayimg" + open-maximized true } -binds { - // Keys consist of modifiers separated by + signs, followed by an XKB key name - // in the end. To find an XKB name for a particular key, you may use a program - // like wev. - // - // "Mod" is a special modifier equal to Super when running on a TTY, and to Alt - // when running as a winit window. - // - // Most actions that you can bind here can also be invoked programmatically with - // `niri msg action do-something`. +// +// KEYBINDINGS +// - // Mod-Shift-/, which is usually the same as Mod-?, - // shows a list of important hotkeys. +binds { Mod+Shift+Slash { show-hotkey-overlay; } - // Suggested binds for running programs: terminal, app launcher, screen locker. - Mod+Return hotkey-overlay-title="Open a Terminal: alacritty" { spawn "alacritty"; } - Mod+Space hotkey-overlay-title="Run an Application: wofi" { spawn "wofi"; } - Super+Alt+L hotkey-overlay-title="Lock the Screen: swaylock" { spawn "swaylock"; } + Mod+Return hotkey-overlay-title="Open a Terminal" { spawn "footclient"; } + Mod+Space hotkey-overlay-title="Search for an Application" { spawn "bemenu-run"; } + Super+Alt+L hotkey-overlay-title="Lock the Screen" { spawn "swaylock"; } + Mod+E hotkey-overlay-title="Open aFilebrowser" { spawn "Thunar"; } + Mod+B hotkey-overlay-title="Open a Web Browser" { spawn "librewolf"; } + Mod+I hotkey-overlay-title="Open a Text Editor" { spawn "footclient" "vim"; } + Mod+W hotkey-overlay-title="Set Wallpaper" { spawn "swayimg" "-g" "/home/blake/images/wallpaper/"; } - // You can also use a shell. Do this if you need pipes, multiple commands, etc. - // Note: the entire command goes as a single argument in the end. - // Mod+T { spawn "bash" "-c" "notify-send hello && exec alacritty"; } + Mod+Q { close-window; } - // Example volume keys mappings for PipeWire & WirePlumber. - // The allow-when-locked=true property makes them work even when the session is locked. - XF86AudioRaiseVolume allow-when-locked=true { spawn "wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.1+"; } - XF86AudioLowerVolume allow-when-locked=true { spawn "wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.1-"; } - XF86AudioMute allow-when-locked=true { spawn "wpctl" "set-mute" "@DEFAULT_AUDIO_SINK@" "toggle"; } - XF86AudioMicMute allow-when-locked=true { spawn "wpctl" "set-mute" "@DEFAULT_AUDIO_SOURCE@" "toggle"; } + // AUDIO + XF86AudioRaiseVolume allow-when-locked=true cooldown-ms=100 { spawn "volume" "up"; } + XF86AudioLowerVolume allow-when-locked=true cooldown-ms=100 { spawn "volume" "down"; } + XF86AudioMute allow-when-locked=true cooldown-ms=100 { spawn "volume" "mute"; } + XF86AudioMicMute allow-when-locked=true cooldown-ms=100 { spawn "volume" "mute" "mic"; } - // Open/close the Overview: a zoomed-out view of workspaces and windows. - // You can also move the mouse into the top-left hot corner, + // OVERVIEW + // Note: you can also move the mouse into the top-left hot corner, // or do a four-finger swipe up on a touchpad. Mod+O repeat=false { toggle-overview; } - Mod+Q { close-window; } - + // FOCUS WINDOW Mod+Up { focus-window-up; } Mod+Down { focus-window-down; } Mod+Left { focus-column-left; } @@ -410,18 +212,19 @@ binds { Mod+J { focus-window-up; } Mod+K { focus-window-down; } - Mod+semicolon { focus-column-right; } Mod+L { focus-column-left; } + Mod+semicolon { focus-column-right; } - Mod+Shift+Up { move-window-up; } - Mod+Shift+Down { move-window-down; } - Mod+Shift+Left { move-column-left; } - Mod+Shift+Right { move-column-right; } + // MOVE WINDOW + Mod+Shift+Up { move-window-up; } + Mod+Shift+Down { move-window-down; } + Mod+Shift+Left { move-column-left; } + Mod+Shift+Right { move-column-right; } - Mod+Shift+J { move-window-up; } - Mod+Shift+K { move-window-down; } - Mod+Shift+L { move-column-left; } - Mod+Shift+semicolon { move-column-right; } + Mod+Shift+J { move-window-up; } + Mod+Shift+K { move-window-down; } + Mod+Shift+L { move-column-left; } + Mod+Shift+semicolon { move-column-right; } // Alternative commands that move across workspaces when reaching // the first or last window in a column. @@ -432,12 +235,14 @@ binds { Mod+Home { focus-column-first; } Mod+End { focus-column-last; } + Mod+Ctrl+Home { move-column-to-first; } Mod+Ctrl+End { move-column-to-last; } - Mod+Ctrl+Left { focus-monitor-left; } - Mod+Ctrl+Down { focus-monitor-down; } + // FOCUS MONITOR Mod+Ctrl+Up { focus-monitor-up; } + Mod+Ctrl+Down { focus-monitor-down; } + Mod+Ctrl+Left { focus-monitor-left; } Mod+Ctrl+Right { focus-monitor-right; } Mod+Ctrl+J { focus-monitor-up; } @@ -445,15 +250,16 @@ binds { Mod+Ctrl+L { focus-monitor-left; } Mod+Ctrl+semicolon { focus-monitor-right; } + // MOVE TO MONITOR Mod+Shift+Ctrl+Up { move-column-to-monitor-up; } Mod+Shift+Ctrl+Down { move-column-to-monitor-down; } Mod+Shift+Ctrl+Left { move-column-to-monitor-left; } Mod+Shift+Ctrl+Right { move-column-to-monitor-right; } - Mod+Shift+Ctrl+J { move-column-to-monitor-up; } - Mod+Shift+Ctrl+K { move-column-to-monitor-down; } - Mod+Shift+Ctrl+L { move-column-to-monitor-left; } - Mod+Shift+Ctrl+semicolon { move-column-to-monitor-right; } + Mod+Shift+Ctrl+J { move-column-to-monitor-up; } + Mod+Shift+Ctrl+K { move-column-to-monitor-down; } + Mod+Shift+Ctrl+L { move-column-to-monitor-left; } + Mod+Shift+Ctrl+semicolon { move-column-to-monitor-right; } // Alternatively, there are commands to move just a single window: // Mod+Shift+Ctrl+Left { move-window-to-monitor-left; } @@ -463,64 +269,40 @@ binds { // Mod+Shift+Ctrl+Left { move-workspace-to-monitor-left; } // ... - Mod+Page_Down { focus-workspace-down; } - Mod+Page_Up { focus-workspace-up; } - Mod+U { focus-workspace-down; } - Mod+I { focus-workspace-up; } - Mod+Ctrl+Page_Down { move-column-to-workspace-down; } - Mod+Ctrl+Page_Up { move-column-to-workspace-up; } - Mod+Ctrl+U { move-column-to-workspace-down; } - Mod+Ctrl+I { move-column-to-workspace-up; } + // WORKSPACE + Mod+U { focus-workspace-up; } + Mod+D { focus-workspace-down; } + + Mod+Ctrl+U { move-column-to-workspace-up; } + Mod+Ctrl+D { move-column-to-workspace-down; } + + Mod+Shift+U { move-workspace-up; } + Mod+Shift+D { move-workspace-down; } // Alternatively, there are commands to move just a single window: // Mod+Ctrl+Page_Down { move-window-to-workspace-down; } // ... - Mod+Shift+Page_Down { move-workspace-down; } - Mod+Shift+Page_Up { move-workspace-up; } - Mod+Shift+U { move-workspace-down; } - Mod+Shift+I { move-workspace-up; } + Mod+Ctrl+WheelScrollUp cooldown-ms=150 { focus-workspace-up; } + Mod+Ctrl+WheelScrollDown cooldown-ms=150 { focus-workspace-down; } - // You can bind mouse wheel scroll ticks using the following syntax. - // These binds will change direction based on the natural-scroll setting. - // - // To avoid scrolling through workspaces really fast, you can use - // the cooldown-ms property. The bind will be rate-limited to this value. - // You can set a cooldown on any bind, but it's most useful for the wheel. - Mod+Ctrl+WheelScrollDown cooldown-ms=150 { focus-workspace-down; } - Mod+Ctrl+WheelScrollUp cooldown-ms=150 { focus-workspace-up; } - Mod+Ctrl+Shift+WheelScrollDown cooldown-ms=150 { move-column-to-workspace-down; } Mod+Ctrl+Shift+WheelScrollUp cooldown-ms=150 { move-column-to-workspace-up; } + Mod+Ctrl+Shift+WheelScrollDown cooldown-ms=150 { move-column-to-workspace-down; } Mod+WheelScrollRight { focus-column-right; } Mod+WheelScrollLeft { focus-column-left; } + Mod+Ctrl+WheelScrollRight { move-column-right; } Mod+Ctrl+WheelScrollLeft { move-column-left; } // Usually scrolling up and down with Shift in applications results in // horizontal scrolling; these binds replicate that. - Mod+WheelScrollDown { focus-column-right; } - Mod+WheelScrollUp { focus-column-left; } + Mod+WheelScrollDown { focus-column-right; } + Mod+WheelScrollUp { focus-column-left; } + Mod+Shift+WheelScrollDown { move-column-right; } Mod+Shift+WheelScrollUp { move-column-left; } - // Similarly, you can bind touchpad scroll "ticks". - // Touchpad scrolling is continuous, so for these binds it is split into - // discrete intervals. - // These binds are also affected by touchpad's natural-scroll, so these - // example binds are "inverted", since we have natural-scroll enabled for - // touchpads by default. - // Mod+TouchpadScrollDown { spawn "wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.02+"; } - // Mod+TouchpadScrollUp { spawn "wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.02-"; } - - // You can refer to workspaces by index. However, keep in mind that - // niri is a dynamic workspace system, so these commands are kind of - // "best effort". Trying to refer to a workspace index bigger than - // the current workspace count will instead refer to the bottommost - // (empty) workspace. - // - // For example, with 2 workspaces + 1 empty, indices 3, 4, 5 and so on - // will all refer to the 3rd workspace. Mod+1 { focus-workspace 1; } Mod+2 { focus-workspace 2; } Mod+3 { focus-workspace 3; } @@ -530,6 +312,7 @@ binds { Mod+7 { focus-workspace 7; } Mod+8 { focus-workspace 8; } Mod+9 { focus-workspace 9; } + Mod+Shift+1 { move-column-to-workspace 1; } Mod+Shift+2 { move-column-to-workspace 2; } Mod+Shift+3 { move-column-to-workspace 3; } @@ -540,69 +323,60 @@ binds { Mod+Shift+8 { move-column-to-workspace 8; } Mod+Shift+9 { move-column-to-workspace 9; } - // Alternatively, there are commands to move just a single window: - // Mod+Ctrl+1 { move-window-to-workspace 1; } + Mod+Ctrl+1 { move-window-to-workspace 1; } + Mod+Ctrl+2 { move-window-to-workspace 2; } + Mod+Ctrl+3 { move-window-to-workspace 3; } + Mod+Ctrl+4 { move-window-to-workspace 4; } + Mod+Ctrl+5 { move-window-to-workspace 5; } + Mod+Ctrl+6 { move-window-to-workspace 6; } + Mod+Ctrl+7 { move-window-to-workspace 7; } + Mod+Ctrl+8 { move-window-to-workspace 8; } + Mod+Ctrl+9 { move-window-to-workspace 9; } - // Switches focus between the current and the previous workspace. - Mod+Tab { focus-workspace-previous; } + Mod+P { focus-workspace-previous; } - // The following binds move the focused window in and out of a column. - // If the window is alone, they will consume it into the nearby column to the side. - // If the window is already in a column, they will expel it out. Mod+BracketLeft { consume-or-expel-window-left; } Mod+BracketRight { consume-or-expel-window-right; } - // Consume one window from the right to the bottom of the focused column. Mod+Comma { consume-window-into-column; } - // Expel the bottom window from the focused column to the right. Mod+Period { expel-window-from-column; } Mod+R { switch-preset-column-width; } Mod+Shift+R { switch-preset-window-height; } Mod+Ctrl+R { reset-window-height; } - Mod+F { maximize-column; } - Mod+Shift+F { fullscreen-window; } - // Expand the focused column to space not taken up by other fully visible columns. - // Makes the column "fill the rest of the space". + Mod+F { maximize-column; } Mod+Ctrl+F { expand-column-to-available-width; } - Mod+C { center-column; } + Mod+M { fullscreen-window; } - // Center all fully visible columns on screen. + Mod+C { center-column; } Mod+Ctrl+C { center-visible-columns; } - // Finer width adjustments. - // This command can also: - // * set width in pixels: "1000" - // * adjust width in pixels: "-5" or "+5" - // * set width as a percentage of screen width: "25%" - // * adjust width as a percentage of screen width: "-10%" or "+10%" - // Pixel sizes use logical, or scaled, pixels. I.e. on an output with scale 2.0, - // set-column-width "100" will make the column occupy 200 physical screen pixels. + // Resize Width Mod+Minus { set-column-width "-10%"; } Mod+Equal { set-column-width "+10%"; } - // Finer height adjustments when in column with other windows. + // Resize Height Mod+Shift+Minus { set-window-height "-10%"; } Mod+Shift+Equal { set-window-height "+10%"; } - // Move the focused window between the floating and the tiling layout. - Mod+V { toggle-window-floating; } - Mod+Shift+V { switch-focus-between-floating-and-tiling; } + // Floating Window + Mod+Tab { toggle-window-floating; } + Mod+Ctrl+Tab { switch-focus-between-floating-and-tiling; } // Toggle tabbed column display mode. // Windows in this column will appear as vertical tabs, // rather than stacked on top of each other. - Mod+W { toggle-column-tabbed-display; } + //Mod+W { toggle-column-tabbed-display; } // Actions to switch layouts. // Note: if you uncomment these, make sure you do NOT have // a matching layout switch hotkey configured in xkb options above. // Having both at once on the same hotkey will break the switching, // since it will switch twice upon pressing the hotkey (once by xkb, once by niri). - // Mod+Space { switch-layout "next"; } - // Mod+Shift+Space { switch-layout "prev"; } + // Mod+Shift+N { switch-layout "next"; } + // Mod+Shift+P { switch-layout "prev"; } Print { screenshot; } Ctrl+Print { screenshot-screen; } |