SNARFER(1)

πŸ“¦ version 0_git20260208, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable

welcome to the SNARFER(1) page, bestie β€” it's from the General Commands Manual and it's all about managing the snarf buffer πŸ«ΆπŸ’–

🌸 NAME 🌸

snarfer β€” manage the snarf buffer πŸ’…

✨ SYNOPSIS ✨

snarfer [ -v ]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so snarfer watches the snarf buffer for changes. Every single time a program changes the snarf buffer contents, snarfer copies the new contents and then takes over control of the buffer. Because the snarf buffer contents are managed by snarfer instead of by individual programs, the contents remain available even after the program that wrote them exits. iconic behavior, honestly πŸ‘‘βœ¨

The -v option is intended for debugging, and it causes snarfer to print the new snarf buffer contents each time it changes πŸŽ€

On Mac OS X, running snarfer keeps the X11 snarf buffer in sync with the Carbon snarf buffer, working around a bug in the OS X X11 server. See getsnarf(3) for more details πŸ“

πŸ“¦ SOURCE πŸ“¦

/src/cmd/snarfer

πŸ‘€ SEE ALSO πŸ‘€

Unix's xclipboard(1), getsnarf(3) πŸ’œ

πŸ’€ BUGS πŸ’€

Both xclipboard and snarfer want sole control of the snarf buffer. Running both at the same time will pass the snarf buffer back and forth between them in an infinite loop 😭 so yeah, do not run both unless you're truly obsessed with infinite chaos.

xoxo, SNARFER(1) β€” that's the footer, bestie πŸ’…βœ¨