From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 4812 invoked from network); 11 May 2022 09:52:02 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 11 May 2022 09:52:02 -0000
Received: from asquith.prosimetrum.com ([125.236.209.157]) by 9front; Wed May 11 05:49:40 -0400 2022
Message-ID: <1A18E2DECEF098E18AA850ABA3BFB26D@prosimetrum.com>
Date: Wed, 11 May 2022 21:49:19 +1200
From: umbraticus@prosimetrum.com
To: 9front@9front.org
In-Reply-To: <94b96400-a26e-4fda-9c38-942c2ec0cf62@sirjofri.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: dependency-scale ACPI lifecycle deep-learning generator 
Subject: Re: [9front] wloc - rc doesn't work because of pid
Reply-To: 9front@9front.org
Precedence: bulk

As the manpage says, it's just an aid to crafting a riostart;
how often are you using wloc?  As is seems good enough.
What if I just ran window with no args, then started myprog
in the new window manually? It's not in your dump thing now
but label probably does give a reasonable idea what's running.

Here's a similar script I use fairly often, to quickly access
another window's text, window, &c.:

for(i in `{walk -dn1,1 /dev/wsys}){
	echo -n $i^'/		# '
	cat $i/label
	echo
}

umbraticus