Change -e/--exec's short option to -x

-e was going to collide with the shape of other single-letter destructive-
ish operational flags; -x frees up the letter and reads fine as
--exec's short form.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gv3s5jckJKzh6JkMoi2Akz

README.md

@@ -58,7 +58,7 @@ slocker-lite -u|--umount <layer-id>
 slocker-lite -c|--cleanup <layer-id>
 slocker-lite -l|--list-images <directory>
 slocker-lite -i|--inspect <image.tar>
-slocker-lite -e|--exec <pid> [-- <command> [args...]]
+slocker-lite -x|--exec <pid> [-- <command> [args...]]
 slocker-lite -k|--kill <pid>
 slocker-lite -v|--volume <name> <directory>
 slocker-lite --list-volumes
@@ -78,7 +78,7 @@ slocker-lite -V|--version
 | `-u, --umount <layer-id>` | Unmount a previously mounted layer (the ID printed by `--mount`/`--run`, or from `containers-storage layers`). |
 | `-c, --cleanup <layer-id>` | Delete a layer and its ancestor chain from local storage (unmount it first). |
 | `-n, --no-nsenter` | With `--run`, bind the mount directly instead of `nsenter`-ing into `fuse-overlayfs`'s namespace. Automatic when running as root; use this to force it off otherwise. |
-| `-D, --daemonize` | With `--run`, fork into the background: detaches from the controlling terminal (`setsid()`), ignores `SIGHUP`, and redirects stdin from `/dev/null` and stdout/stderr to a log file under `$XDG_STATE_HOME/slocker-lite/logs/`. Prints the session's pid and log path, then returns — the same pid `--list-processes`/`-e/--exec` use. |
+| `-D, --daemonize` | With `--run`, fork into the background: detaches from the controlling terminal (`setsid()`), ignores `SIGHUP`, and redirects stdin from `/dev/null` and stdout/stderr to a log file under `$XDG_STATE_HOME/slocker-lite/logs/`. Prints the session's pid and log path, then returns — the same pid `--list-processes`/`-x/--exec` use. |
 | `--user <user>` | With `--run`, run the command as this user (name or numeric uid) instead of the image's own declared user (or root, if it declares none). Resolved against the image's own `/etc/passwd`. Only takes effect when `--run` executes as root. |
 | `--group <group>` | With `--user`, use this group (name or numeric gid) instead of the user's primary group. |
 | `--hostname <name>` | With `--run`, set the sandbox's hostname. Only takes effect if the running kernel supports `--unshare-uts`; ignored with a warning otherwise. |
@@ -86,7 +86,7 @@ slocker-lite -V|--version
 | `--env-file <file>` | With `--run`, load environment variables from `<file>` — one `VAR=VALUE` per line; blank lines and `#`-comments are skipped. Repeatable. |
 | `-l, --list-images <dir>` | List OCI Image Layout tars (`*.tar`, `*.tar.*`) found directly in `<dir>`, with their `name:tag`. |
 | `-i, --inspect <image.tar>` | Print an image's declared user, exposed ports, env, volumes, and default command, without mounting or running it. |
-| `-e, --exec <pid>` | Join an already-running `--run` session (`<pid>` must be one `--list-processes` shows as `running`) and run a command inside its container. Pass `-- <command> [args...]` to specify it. |
+| `-x, --exec <pid>` | Join an already-running `--run` session (`<pid>` must be one `--list-processes` shows as `running`) and run a command inside its container. Pass `-- <command> [args...]` to specify it. |
 | `-k, --kill <pid>` | Stop a running `--run` session (`<pid>` must be one `--list-processes` shows as `running`): sends `SIGTERM`, waits up to 10s, then forces it with `SIGKILL`. Reaches every process the session started — including daemonized/reparented ones a plain `kill <pid>` would leave behind — via a dedicated cgroup when available, or the sandboxed pid namespace's own collapse-on-kill guarantee when not, falling back to signaling the tracked pid alone if neither applies. |
 | `-v, --volume <name> <dir>` | Create a named volume mapped to a host directory (created if missing), recorded in the config file's `volumes` section. Fails if the name or directory is already used by an existing volume. Volume names can't contain `/`. With `--run`, instead mounts a volume into the sandbox (repeatable): `<name>` is an existing named volume, or, if it contains `/`, a host directory path (created if missing); `<dir>` is the absolute path inside the container to mount it at. If the host directory is empty and the image already has content there, that content is copied in first, preserving numeric ownership/permissions/links and, where the host filesystem supports them, extended attributes/ACLs (skipped with a warning otherwise). |
 | `--list-volumes` | List all named volumes (see `-v/--volume`) with their host directory. |
@@ -206,7 +206,7 @@ when its own session ends, but `--clean-processes` removes any stale ones left
 behind (e.g. after a crash) using that same check, atomically per file, so it
 never removes one that's still genuinely running.
 
-`-e/--exec <pid>` joins a running session's namespaces with `nsenter` and runs a
+`-x/--exec <pid>` joins a running session's namespaces with `nsenter` and runs a
 command there. Because `bwrap` itself sets up the sandbox's mount/user namespaces
 and then hands the actual sandboxed command off to a child process in fresh
 pid/uts/ipc/cgroup namespaces, `-e` resolves that real child first (via `/proc`)
@@ -239,7 +239,7 @@ at once (`exec()` never changes session membership), and correctly scopes
 `bwrap`'s own `--die-with-parent` to that child. The child ignores `SIGHUP` and
 redirects output to a log file before doing anything else; the original,
 still-foreground process waits only long enough to learn the real session pid
-(the same one `--list-processes`/`-e/--exec` use) before printing it and
+(the same one `--list-processes`/`-x/--exec` use) before printing it and
 returning — the detached child is what runs the entire session afterward,
 including the same unmount/cleanup that always ran once the sandboxed command
 exits.