FLUXBOX-REMOTE(1)

πŸ“¦
version 1.3.7+248+g5ba8c921 Β· 2 versions
  • 1.3.7+248+g5ba8c921 Β· alpine 3.24, arch rolling, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.3.5 Β· debian bookworm, ubuntu jammy
, in alpine 3.24, arch rolling, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– FLUXBOX-REMOTE πŸ’–

okay so bestie, welcome to the fluxbox-remote(1) manual page β€” it lives in the Fluxbox Manual and it's literally your little backstage pass to fluxbox(1). sit down, hydrate, let's go 🫢


✨ NAME ✨

fluxbox-remote β€” command line access to key commands for fluxbox(1) πŸ’…


🌸 SYNOPSIS 🌸

fluxbox-remote command

πŸ¦‹ DESCRIPTION πŸ¦‹

so like, fluxbox-remote(1) was designed to let scripts execute most of the key commands from fluxbox(1). no cap, that's the whole job.

but β€” and this is the important part β€” fluxbox-remote(1) will only work with fluxbox(1). its communications with fluxbox(1) are not standardized in any way. not even a little. it's giving ✨situationship✨, not a real protocol.

so it is recommended that a standards-based tool such as wmctrl(1) be used whenever possible, in order for scripts to work with other window managers. iykyk πŸ‘‘

πŸ’€ CAVEATS πŸ’€

not me having to deliver the scary part 😭

fluxbox-remote(1) uses the X11 protocol to communicate with fluxbox(1). therefore, it is possible for any user with access to the X(7) server to use fluxbox-remote(1). yes, any. πŸ™ˆ

for this reason, several key commands have been disabled.

users should be aware of the security implications when enabling fluxbox-remote(1), especially when using a forwarded X(7) connection. fr fr, this one is not a vibe β€” read it twice. πŸ”₯

πŸŽ€ RESOURCES πŸŽ€

  • session.screen0.allowRemoteActions: <boolean> β€” this resource in ~/.fluxbox/init must be set to 'true' in order for fluxbox-remote(1) to function. and bestie, please read the CAVEATS first. please. πŸ™

🌈 ENVIRONMENT 🌈

in order to communicate with fluxbox(1), the DISPLAY environment variable must be set properly. usually, the value should be ':0.0'. πŸ–₯️✨


πŸ‘‘ AUTHORS πŸ‘‘

this man page written by Mark Tiefenbruck <mark at fluxbox.org> πŸ’œ


πŸ”₯ SEE ALSO πŸ”₯


⭐ AUTHOR ⭐

Mark Tiefenbruck <mark@fluxbox.org>

  • Author.

and that's the whole page, bestie! 🧚 this one came from fluxbox-remote.txt, dated 08 February 2015 β€” yes it's an older icon but she still ate, periodt πŸ’…πŸŒΈπŸ¦‹πŸ“