XON(1)

🎀 XON(1) — NAME 🎀

okay so this is XON(1) from the General Commands Manual, and the command is xon: it starts an X program on a remote machine. bestie, remote-launch queen behavior.

---

✨ SYNOPSIS ✨

xon remote-host [-access] [-debug] [-name window-name] [-nols] [-screen screen-no] [-user user-name] [command ...]

---

💖 DESCRIPTION 💖

xon runs the command you specify — default is xterm -ls — on the remote machine using rsh, remsh, or rcmd. It passes the DISPLAY, XAUTHORITY and XUSERFILESEARCHPATH environment variables to the remote command. slay.

When no command is specified, xon runs xterm -ls. It additionally specifies the application name to be xterm-remote-host and the window title to be -fIremote-host. iconic little defaults, honestly.

hard requirement, no cap: xon can only work when the remote host will allow you to log in without a password, by having an entry in the .rhosts file permitting access. that's the whole gatekeeping situation.

---

🌈 OPTIONS 🌈

quick vibe check: the options follow the remote host name — as they do with rlogin.

• -access — runs xhost locally to add the remote host to the host access list in the X server. This won't work unless xhost is given permission to modify the access list. permission check, bestie.
• -debug — normally, xon disconnects the remote process from stdin, stdout and stderr to eliminate the daemon processes which usually connect them across the network. Specifying the -debug option leaves them connected so that error messages from the remote execution are sent back to the originating host. very "keep the receipts connected" energy.
• -name window-name — this specifies a different application name and window title for the default command (xterm). custom name, custom title, custom slay.
• -nols — normally xon passes the -ls option to the remote xterm; this option suspends that behaviour. it's the "not today, -ls" button.
• -screen screen-no — this changes the screen number of the DISPLAY variable passed to the remote command. screen number switch-up, periodt.
• -user user-name — by default, xon simply uses rsh/remsh/rcmd to connect to the remote machine using the same user name as on the local machine. This option causes xon to specify an alternative user name. This will not work unless you have authorization to access the remote account, by placing an appropriate entry in the remote user's .rhosts file. authorization tea, iykyk.

---

💀 BUGS 💀

• xon can get easily confused when the remote-host, user-name or various environment variable values contain white space. 😭 white space really said "plot twist."
• xon has no way to send the appropriate X authorization information to the remote host. and that's just the limitation, bestie.

---

that's the whole page 🫶 this manual came from X Version 11, scripts 1.0.1 — slay, periodt, and remember: options go after the remote host 💅