Skip to main content

max / alloy

1.3 KB · 25 lines History Blame Raw
1 # Wayland backend hints for toolkit apps under the Alloy sway session.
2 # Was niri's `environment {}` block; moved here so it applies to the
3 # whole user session rather than only sway's direct children.
4 # Verify these reach GTK/Qt apps when sway is launched via greetd
5 # (see the live-system verification GO task).
6 GDK_BACKEND=wayland,x11
7 QT_QPA_PLATFORM=wayland;xcb
8 # The image no longer ships Gecko, but Firefox is one builder choice away
9 # and this variable is inert without it. It stays as a toolkit hint like
10 # the two above, not as browser configuration.
11 MOZ_ENABLE_WAYLAND=1
12
13 # gopass copies through Alloy's private clipboard path rather than calling
14 # wl-copy itself, so a password never reaches the clipboard history that the
15 # sway config's two watchers fill. Without these two lines gopass finds
16 # wl-copy on its own and the leak is back (GO alloy problem e7a9e38c).
17 #
18 # gopass names both variables in its own "no clipboard available" message, so
19 # this is the documented seam rather than a discovered one. Both are needed:
20 # the copy half marks the selection private, the clear half unmarks it, and
21 # setting only the first would pause clipboard history until the backstop
22 # fired.
23 GOPASS_CLIPBOARD_COPY_CMD=/usr/bin/alloy-secret-copy
24 GOPASS_CLIPBOARD_CLEAR_CMD=/usr/bin/alloy-secret-clear
25