Give the remaining tray applets their modules, each with one start
openrazer (the official driver, daemon and library), polychromatic (the AUR tray, kept as found; its i3 line moves out of the i3 module into its own node-display-session contribution), forticlient (the AUR VPN client: its service declared, its configuration never read) and nm-applet (the desktop half of NetworkManager, apart from the server-side module). The openrazer daemon fails on both workstations because the account is not in the openrazer group; openrazer_check names it and the README carries the one-off step, since the account's user resource is zsh's. desktop.go learns to tell a program from another sharing its 15-character command name, so polychromatic's tools never count or end themselves, and a copies test holds the six carriers to one text.
This commit is contained in:
@@ -106,9 +106,15 @@ The person's list keeps every line as found, the dropped ones included. `xdg_che
|
||||
## Autostart: listed, not owned
|
||||
|
||||
An XDG autostart entry belongs to the module of the application it starts, as `picom` does: picom's
|
||||
package entry is its one starter. A future `nextcloud-client` module owns `Nextcloud.desktop` (the
|
||||
client writes it itself), a blueman module beside `bluetooth` owns blueman's, and Slack's and JetBrains
|
||||
Toolbox's entries would be their modules'.
|
||||
package entry is its one starter. `nextcloud-client` holds `Nextcloud.desktop` as its start (the client
|
||||
writes it itself), and `blueman`, `nm-applet` and `forticlient` hold their packages' entries as theirs.
|
||||
`polychromatic`'s helper entry is that module's too, though the tray's start is its window-manager line.
|
||||
Slack's and JetBrains Toolbox's entries would be their modules'. Two entries on the desktop have no
|
||||
module and are left as found: the print applet's (the `cups` README says why) and geoclue's demo
|
||||
agent (`/usr/lib/geoclue-2.0/demos/agent`). geoclue is there as a dependency of an application of the
|
||||
operator's, not as a choice; the agent is what answers geoclue's question "may this program know
|
||||
where the machine is" outside GNOME, whose own shell answers it there. It is a dependency's piece, so
|
||||
it belongs to whoever installs geoclue on purpose, and nobody does yet.
|
||||
This module only says what is there, and what the session does with it.
|
||||
|
||||
The session's starter is `i3`'s `dex --autostart --environment i3`. `xdg_autostart` decides each
|
||||
|
||||
Reference in New Issue
Block a user