aboutsummaryrefslogtreecommitdiff
path: root/client-protocol.h (follow)
Commit message (Collapse)AuthorAgeLines
* spawn-terminal: spawn with all the original command line optionsspawn-terminal-cmdline-argumentsDaniel Eklöf6 days-3/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this, spawn-terminal would spawn a new foot or footclient, but *without* any of the command line options the user started the original foot/footclient with. We did have a hack for --config, but all other options were forgotten in the new instance. This patch fixes this. * term_init() stores the raw argc/argv in the terminal struct. * term_spawn_new() calls spawn() with the stored argc/argv. * for single instances, main() calls term_init() with the unparsed argc/argv. * the client/server protocol is extended to always send the raw argc/argv to the server. * the server calls term_init() with the argc/argv from the client. * bonus: on linux, we now use /proc/self/exe to determine which binary to launch. This means if you run e.g. a foot from your build tree, spawn-terminal will exec _that_ foot, not the system foot. A couple of behavioral changes, and/or side-effects, caused by the above (not exhaustive): * footclient -E: spawn-terminal will not use the _exact_ environment from the original footclient, but will simply pass -E to the new footclient. This means the new instance will inherit the *current* environment of the original instance. * foot htop: spawn-instance will _also_ launch a new foot+htop. Before this patch, spawn-instance would launch a new foot+shell. Closes #1622
* server/client: add support for sending SIGUSR to footclientDaniel Eklöf2025-08-01-0/+14
| | | | | | | | | | | This patch adds the IPC infrastructure necessary to propagate SIGUSR1/SIGUSR2 from a footclient process to the server process. By targeting a particular footclient instance, only that particular instance changes theme. This is different from when targeting the server process, where all instances change theme. Closes #2156
* client: add -E,--client-environmentDaniel Eklöf2022-04-12-1/+3
| | | | | | | | | | | | | | | | | When this option is used, the child process in the new terminal instance will inherit its environment from the footclient process, instead of the foot server’s. Implemented by sending (yet another) dynamic string list as part of the client -> server setup packet. When the new option is *not* used, the setup packet is now 2 bytes larger than before. On the server side, the slave process now uses execvpe() instead of execvp(). There’s plumbing to propagate a new ‘envp’ argument from term_init() all the way down to slave_exec(). If ‘envp’ is NULL, we use ‘environ’ instead (thus matching the old behavior of execvp()). Closes #1004
* foot/client: implement xdga client activationRonan Pigott2021-11-01-2/+5
| | | | | | | | | | | This is an application of the xdg activation protocol that will allow compositors to associate new foot toplevels with the command that launched them. footclient receives an activation token from the launcher which the compositor can use to track application startup. It passes the token to the foot server, which then activates the new window with the token to complete the startup sequence.
* client: send overrides for everything that is publicly visible in the confDaniel Eklöf2021-06-23-19/+10
| | | | | | | | | Send a generic “overrides” list to the server, containing options in text, on the format “section.key=value”. This reduces the size of the base client/server protocol packet, as well as opens up for a generic -o,--override command line option (not yet implemented).
* add option to detach the client process from the terminal instanceFelipe Trzaskowski2021-03-13-0/+1
|
* client: add "--window-size-pixels" and "--window-size-chars" optionsCraig Barnes2020-11-22-0/+3
|
* client-protocol: codespell: stati -> staticDaniel Eklöf2020-11-21-1/+1
|
* client/server: simplify setup packet handlingDaniel Eklöf2020-11-21-0/+31
Instead of writing (and logging errors for) every parameter, one at a time, send all fixed size data in a single struct, followed by all the variable length data.