SNARFER(1)
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 π
Bothxclipboardandsnarferwant 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 π β¨
π¦ where this page comes from
- alpine 3.24: plan9port-doc 0_git20260208-r0 Β· LPL-1.02
- arch rolling: plan9port 20261021-2 Β· custom
- nixos 26.05: plan9port 0-unstable-2025-11-10
- nixos 26.05: plan9port-wayland 0-unstable-2025-11-26
- nixpkgs unstable: plan9port 0-unstable-2025-11-10
- nixpkgs unstable: plan9port-wayland 0-unstable-2025-11-26
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms