#tail for moonx

Version 0.2.1 behavior is documented here. The support record separates local verification from published MoonX behavior; moonx examples use registry releases.

Print the last lines or bytes of files or stdin:

printf '1\n2\n3\n4\n' | moonx cli/tail -n 2
printf '1\n2\n3\n4\n' | moonx cli/tail -n +3   # from line 3 to the end
moonx cli/tail -n 100 huge.log

Options: -n N last N lines (default 10), -n +K from line K, -c N last N bytes, -c +K from byte K, -q/-v header control, -f/--follow to follow an open file descriptor, and -s SEC/--sleep-interval SEC to set the polling interval (default 1 second).

The observed file paths produced the requested line/byte suffixes and +K forms. Follow mode emits the initial selection, then emits bytes appended to each regular file. A file truncated in place is followed from byte zero. The descriptor remains open across renames, matching tail -f; deleting and recreating a path is not followed, because -F is not implemented.

-F remains a tested status-2 rejection. Faithful replacement detection needs public file identity, which the released filesystem API does not expose; reopening a path is available but alone does not establish that the file was replaced. See ADR-0004.

With no file operand, -f silently reads stdin through EOF and exits, matching the upstream finite-pipe behavior. Regular-file follow is polling-based and works on the native and Wasm targets; it does not require host file-notify APIs.

#Standalone metadata

Standalone --version prints exactly tail 0.2.1 followed by one newline. Standalone --help starts with Usage: tail, lists both metadata options, and ends with a newline. Both write to stdout, leave stdin unread, and exit with status 0. Exact-version publication and verification remain recorded separately in the support record.

Source Files

main.mbt

Site source Report issue Packages Build queue Skills Statistics