add niri conf, fork xdg-open
Jes Olson j3s@c3f.net
Sun, 24 Mar 2024 16:02:33 -0500
2 files changed,
609 insertions(+),
0 deletions(-)
A
.config/niri/config.kdl
@@ -0,0 +1,597 @@
+// This config is in the KDL format: https://kdl.dev +// "/-" comments out the following node. + +input { + keyboard { + xkb { + // You can set rules, model, layout, variant and options. + // For more information, see xkeyboard-config(7). + + // For example: + // layout "us,ru" + // options "grp:win_space_toggle,compose:ralt,ctrl:nocaps" + } + + // You can set the keyboard repeat parameters. The defaults match wlroots and sway. + // Delay is in milliseconds before the repeat starts. Rate is in characters per second. + // repeat-delay 600 + // repeat-rate 25 + + // Niri can remember the keyboard layout globally (the default) or per-window. + // - "global" - layout change is global for all windows. + // - "window" - layout is tracked for each window individually. + // track-layout "global" + } + + // Next sections include libinput settings. + // Omitting settings disables them, or leaves them at their default values. + touchpad { + tap + // dwt + // dwtp + // natural-scroll + // accel-speed 0.2 + // accel-profile "flat" + // tap-button-map "left-middle-right" + } + + mouse { + // natural-scroll + // accel-speed 0.2 + // accel-profile "flat" + } + + trackpoint { + // natural-scroll + // accel-speed 0.2 + // accel-profile "flat" + } + + tablet { + // Set the name of the output (see below) which the tablet will map to. + // If this is unset or the output doesn't exist, the tablet maps to one of the + // existing outputs. + map-to-output "eDP-1" + } + + touch { + // Set the name of the output (see below) which touch input will map to. + // If this is unset or the output doesn't exist, touch input maps to one of the + // existing outputs. + map-to-output "eDP-1" + } + + // By default, niri will take over the power button to make it sleep + // instead of power off. + // Uncomment this if you would like to configure the power button elsewhere + // (i.e. logind.conf). + // disable-power-key-handling +} + +// 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". +// Remember to uncomment the node by removing "/-"! +output "eDP-1" { + // Uncomment this line to disable this output. + // off + + // Scale is a floating-point number, but at the moment only integer values work. + scale 2.0 + + // 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" + + // 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 "1920x1080" + + // 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 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. + // It the position is unset or results in an overlap, the output is instead placed + // automatically. + position x=1280 y=0 +} + +layout { + // 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. + + // 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. + width 3 + + // 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" + + // Additionally, there's a legacy RGBA syntax: + // active-color 127 200 255 255 + + // 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. + // + // active-gradient from="#80c8ff" to="#bbddff" 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="#505050" 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" + + // active-gradient from="#ffbb66" to="#ffc880" angle=45 relative-to="workspace-view" + // inactive-gradient from="#505050" to="#808080" angle=45 relative-to="workspace-view" + } + + // You can customize the widths that "switch-preset-column-width" (Mod+R) toggles between. + 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 + } + + // You can change the default width of the new windows. + default-column-width { proportion 0.5; } + // If you leave the brackets empty, the windows themselves will decide their initial width. + // default-column-width {} + + // Set gaps around windows in logical pixels. + gaps 4 + + // 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 + } + + // 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. + // - "on-overflow", focusing a column will center it if it doesn't fit + // together with the previously focused column. + // - "always", the focused column will always be centered. + center-focused-column "never" +} + +// 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. +// spawn-at-startup "alacritty" "-e" "fish" + +// You can override environment variables for processes spawned by niri. +environment { + // Set a variable like this: + // QT_QPA_PLATFORM "wayland" + + // Remove a variable by using null as the value: + // DISPLAY null +} + +cursor { + // Change the theme and size of the cursor as well as set the + // `XCURSOR_THEME` and `XCURSOR_SIZE` env variables. + // xcursor-theme "default" + // xcursor-size 24 +} + +// 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. +// Additionally, clients will be informed that they are tiled, removing some rounded corners. +// 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" + +// You can also set this to null to disable saving screenshots to disk. +// screenshot-path null + +// Settings for the "Important Hotkeys" overlay. +hotkey-overlay { + // Uncomment this line if you don't want to see the hotkey help at niri startup. + // skip-at-startup +} + +// Animation settings. +animations { + // Uncomment to turn off all animations. + // off + + // Slow down all animations by this factor. Values below 1 speed them up instead. + // slowdown 3.0 + + // You can configure all individual animations. + // Available settings are the same for all of them. + // - off disables the animation. + // + // Niri supports two animation types: easing and spring. + // You can set properties for only ONE of them. + // + // Easing has the following settings: + // - duration-ms sets the duration of the animation in milliseconds. + // - curve sets the easing curve. Currently, available curves + // are "ease-out-cubic" and "ease-out-expo". + // + // Spring animations work better with touchpad gestures, because they + // take into account the velocity of your fingers as you release the swipe. + // The parameters are less obvious and generally should be tuned + // with trial and error. Notably, you cannot directly set the duration. + // You can use this app to help visualize how the spring parameters + // change the animation: https://flathub.org/apps/app.drey.Elastic + // + // A spring animation is configured like this: + // - spring damping-ratio=1.0 stiffness=1000 epsilon=0.0001 + // + // The damping ratio goes from 0.1 to 10.0 and has the following properties: + // - below 1.0: underdamped spring, will oscillate in the end. + // - above 1.0: overdamped spring, won't oscillate. + // - 1.0: critically damped spring, comes to rest in minimum possible time + // without oscillations. + // + // However, even with damping ratio = 1.0 the spring animation may oscillate + // if "launched" with enough velocity from a touchpad swipe. + // + // Lower stiffness will result in a slower animation more prone to oscillation. + // + // Set epsilon to a lower value if the animation "jumps" in the end. + // + // The spring mass is hardcoded to 1.0 and cannot be changed. Instead, change + // stiffness proportionally. E.g. increasing mass by 2x is the same as + // decreasing stiffness by 2x. + + // Animation when switching workspaces up and down, + // including after the touchpad gesture. + workspace-switch { + // off + // spring damping-ratio=1.0 stiffness=1000 epsilon=0.0001 + } + + // All horizontal camera view movement: + // - When a window off-screen is focused and the camera scrolls to it. + // - When a new window appears off-screen and the camera scrolls to it. + // - When a window resizes bigger and the camera scrolls to show it in full. + // - And so on. + horizontal-view-movement { + // off + // spring damping-ratio=1.0 stiffness=800 epsilon=0.0001 + } + + // Window opening animation. Note that this one has different defaults. + window-open { + // off + // duration-ms 150 + // curve "ease-out-expo" + + // Example for a slightly bouncy window opening: + // spring damping-ratio=0.8 stiffness=1000 epsilon=0.0001 + } + + // Config parse error and new default config creation notification + // open/close animation. + config-notification-open-close { + // off + // spring damping-ratio=0.6 stiffness=1000 epsilon=0.001 + } +} + +// Window rules let you adjust behavior for individual windows. +// They are processed in order of appearance in this file. +// (This example rule is commented out with a "/-" in front.) +/-window-rule { + // Match directives control which windows this rule will apply to. + // You can match by app-id and by title. + // The window must match all properties of the match directive. + match app-id="org.myapp.MyApp" title="My Cool App" + + // There can be multiple match directives. A window must match any one + // of the rule's match directives. + // + // If there are no match directives, any window will match the rule. + match title="Second App" + + // You can also add exclude directives which have the same properties. + // If a window matches any exclude directive, it won't match this rule. + // + // Both app-id and title are regular expressions. + // Raw KDL strings are helpful here. + exclude app-id=r#"\.unwanted\."# + + // Here are the properties that you can set on a window rule. + // You can override the default column width. + default-column-width { proportion 0.75; } + + // You can set the output that this window will initially open on. + // If such an output does not exist, it will open on the currently + // focused output as usual. + open-on-output "eDP-1" + + // Make this window open as a maximized column. + open-maximized true + + // Make this window open fullscreen. + open-fullscreen true + // You can also set this to false to prevent a window from opening fullscreen. + // open-fullscreen false +} + +// Here's a useful example. Work around WezTerm's initial configure bug +// by setting an empty default-column-width. +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. + // The regular expression can match anywhere in the string. + match app-id=r#"^org\.wezfurlong\.wezterm$"# + default-column-width {} +} + +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`. + + // Mod-Shift-/, which is usually the same as Mod-?, + // shows a list of important hotkeys. + Mod+Shift+Slash { show-hotkey-overlay; } + + // Suggested binds for running programs: terminal, app launcher, screen locker. + Mod+Return { spawn "foot"; } + Mod+D { spawn "fuzzel"; } + Mod+Shift+L { spawn "swaylock"; } + + // You can also use a shell: + // Mod+T { spawn "bash" "-c" "notify-send hello && exec alacritty"; } + + // Example volume keys mappings for PipeWire & WirePlumber. + XF86AudioRaiseVolume { spawn "wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.1+"; } + XF86AudioLowerVolume { spawn "wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.1-"; } + + Mod+Shift+Q { close-window; } + + Mod+Left { focus-column-left; } + Mod+Down { focus-window-down; } + Mod+Up { focus-window-up; } + Mod+Right { focus-column-right; } + Mod+H { focus-column-left; } + Mod+J { focus-window-down; } + Mod+K { focus-window-up; } + Mod+L { focus-column-right; } + + Mod+Ctrl+Left { move-column-left; } + Mod+Ctrl+Down { move-window-down; } + Mod+Ctrl+Up { move-window-up; } + Mod+Ctrl+Right { move-column-right; } + Mod+Ctrl+H { move-column-left; } + Mod+Ctrl+J { move-window-down; } + Mod+Ctrl+K { move-window-up; } + Mod+Ctrl+L { move-column-right; } + + // Alternative commands that move across workspaces when reaching + // the first or last window in a column. + // Mod+J { focus-window-or-workspace-down; } + // Mod+K { focus-window-or-workspace-up; } + // Mod+Ctrl+J { move-window-down-or-to-workspace-down; } + // Mod+Ctrl+K { move-window-up-or-to-workspace-up; } + + 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+Shift+Left { focus-monitor-left; } + // Mod+Shift+Down { focus-monitor-down; } + // Mod+Shift+Up { focus-monitor-up; } + // Mod+Shift+Right { focus-monitor-right; } + // Mod+Shift+H { focus-monitor-left; } + // Mod+Shift+J { focus-monitor-down; } + // Mod+Shift+K { focus-monitor-up; } + // Mod+Shift+L { focus-monitor-right; } + + Mod+Shift+Ctrl+Left { move-column-to-monitor-left; } + Mod+Shift+Ctrl+Down { move-column-to-monitor-down; } + Mod+Shift+Ctrl+Up { move-column-to-monitor-up; } + Mod+Shift+Ctrl+Right { move-column-to-monitor-right; } + Mod+Shift+Ctrl+H { move-column-to-monitor-left; } + Mod+Shift+Ctrl+J { move-column-to-monitor-down; } + Mod+Shift+Ctrl+K { move-column-to-monitor-up; } + Mod+Shift+Ctrl+L { move-column-to-monitor-right; } + + // Alternatively, there are commands to move just a single window: + // Mod+Shift+Ctrl+Left { move-window-to-monitor-left; } + // ... + + // And you can also move a whole workspace to another monitor: + // 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; } + + // 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; } + + // 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; } + Mod+4 { focus-workspace 4; } + Mod+5 { focus-workspace 5; } + Mod+6 { focus-workspace 6; } + Mod+7 { focus-workspace 7; } + Mod+8 { focus-workspace 8; } + Mod+9 { focus-workspace 9; } + Mod+Ctrl+1 { move-column-to-workspace 1; } + Mod+Ctrl+2 { move-column-to-workspace 2; } + Mod+Ctrl+3 { move-column-to-workspace 3; } + Mod+Ctrl+4 { move-column-to-workspace 4; } + Mod+Ctrl+5 { move-column-to-workspace 5; } + Mod+Ctrl+6 { move-column-to-workspace 6; } + Mod+Ctrl+7 { move-column-to-workspace 7; } + Mod+Ctrl+8 { move-column-to-workspace 8; } + Mod+Ctrl+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+Comma { consume-window-into-column; } + Mod+Period { expel-window-from-column; } + + // There are also commands that consume or expel a single window to the side. + // Mod+BracketLeft { consume-or-expel-window-left; } + // Mod+BracketRight { consume-or-expel-window-right; } + + Mod+R { switch-preset-column-width; } + Mod+F { maximize-column; } + Mod+Shift+F { fullscreen-window; } + Mod+C { center-column; } + + // 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. + Mod+Minus { set-column-width "-10%"; } + Mod+Equal { set-column-width "+10%"; } + + // Finer height adjustments when in column with other windows. + Mod+Shift+Minus { set-window-height "-10%"; } + Mod+Shift+Equal { set-window-height "+10%"; } + + // 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"; } + + Print { screenshot; } + Ctrl+Print { screenshot-screen; } + Alt+Print { screenshot-window; } + + // The quit action will show a confirmation dialog to avoid accidental exits. + // If you want to skip the confirmation dialog, set the flag like so: + // Mod+Shift+E { quit skip-confirmation=true; } + Mod+Shift+E { quit; } + + Mod+Shift+P { power-off-monitors; } + + // This debug bind will tint all surfaces green, unless they are being + // directly scanned out. It's therefore useful to check if direct scanout + // is working. + // Mod+Shift+Ctrl+T { toggle-debug-tint; } +} + +// Settings for debugging. Not meant for normal use. +// These can change or stop working at any point with little notice. +debug { + // Make niri take over its DBus services even if it's not running as a session. + // Useful for testing screen recording changes without having to relogin. + // The main niri instance will *not* currently take back the services; so you will + // need to relogin in the end. + // dbus-interfaces-in-non-session-instances + + // Wait until every frame is done rendering before handing it over to DRM. + // wait-for-frame-completion-before-queueing + + // Enable direct scanout into overlay planes. + // May cause frame drops during some animations on some hardware. + // enable-overlay-planes + + // Disable the use of the cursor plane. + // The cursor will be rendered together with the rest of the frame. + // disable-cursor-plane + + // Override the DRM device that niri will use for all rendering. + // render-drm-device "/dev/dri/renderD129" + + // Enable the color-transformations capability of the Smithay renderer. + // May cause a slight decrease in rendering performance. + // enable-color-transformations-capability + + // Emulate zero (unknown) presentation time returned from DRM. + // This is a thing on NVIDIA proprietary drivers, so this flag can be + // used to test that we don't break too hard on those systems. + // emulate-zero-presentation-time +}
A
bin/rose/xdg-open
@@ -0,0 +1,12 @@
+#!/bin/sh +case "${1%%:*}" in + http|https) + exec firefox "$1" + ;; + *.pdf) + exec zathura "$1" + ;; + *) + exec /usr/bin/xdg-open "$@" + ;; +esac