Local for(i in pi^(1 2 3 4 5 6 7) trixie) rfs pi@$i
B /n/pi1 /n/pi2 /n/pi3 /n/pi4 /n/pi5 /n/pi6 /n/pi7 /n/trixie
Edit X!/n/[^/]+/$! >echo -n 'Edit ' > /mnt/acme/$winid/tag

Edit X!Errors! D

Edit X!/n/[^/]+/$! >dircpu &
Edit X!/n/[^/]+/$! >r uptime &
Edit X!/n/[^/]+/$! >r cat /sys/firmware/devicetree/base/model &
Edit X!/n/[^/]+/$! >r vcgencmd get_config total_mem &
Edit X!/n/[^/]+/$! >r ip addr &
Edit X!/n/[^/]+/$! >r df -h / &

Edit X!Errors! >r sudo apt update &
Edit X!Errors! ,g/All packages are up to date./ D
Edit X!Errors! >r sudo apt upgrade -y &
# Edit X!Errors! >r sudo reboot &

Edit X!/n/[^/]+/$! >r uname -a &
Edit X!Errors! ,g/aarch64/ D
Edit X!Errors! ,v/armv6l/ D

Edit B <echo /n/*/boot/firmware/cmdline.txt
Edit X!/cmdline.txt! D

echo $home/lib/plumbing
╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍✃╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍ 
# remote absolute path dir names go to editor
type is text
data matches '(/[.a-zA-Z¡-￿0-9_/+\-]*[a-zA-Z¡-￿0-9_/+\!\-])'
wdir matches '(/n/[^/]+)(/.*)?'
arg isdir	$1/$data
data set	$dir
plumb to edit
plumb client $editor

# remote absolute path file names, possibly tagged by line number, go to editor
type is text
wdir matches '(/n/[^/]+)(/.*)?'
data matches '(/[.a-zA-Z¡-￿0-9_/+\-]*[a-zA-Z¡-￿0-9_/+\!\-])('$addr')?'
attr add	addr=$3
data set	$1
wdir matches '(/n/[^/]+)(/.*)?'
arg isfile	$1/$data
data set	$file
plumb to edit
plumb client $editor

# NOTE: the effect of 'data set' and 'attr add' of a partially matched rule (above) persists through the rest of the rules!
#
# From the plumb(7) manpage:
# "Such rewritings are permanent, so rules that specify them should
# be placed after all pattern-matching rules in the rule set."
#
# yrk: I haven't found a way to avoid that, as I need to capture
# context from both 'data matches' and 'wdir matches' for the 'arg isfile' there.
╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍✃╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍