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 16251 invoked from network); 11 May 2022 11:11:11 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 11 May 2022 11:11:11 -0000 Received: from sirjofri.de ([5.45.105.127]) by 9front; Wed May 11 07:08:37 -0400 2022 Received: from sirjofri.de ([95.90.218.92]) by sirjofri.de; Wed May 11 13:08:36 +0200 2022 Date: Wed, 11 May 2022 11:08:34 +0000 (UTC) From: sirjofri To: 9front@9front.org Message-ID: In-Reply-To: References: <1A18E2DECEF098E18AA850ABA3BFB26D@prosimetrum.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Correlation-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: distributed YAML over YAML cloud table Subject: Re: [9front] wloc - rc doesn't work because of pid Reply-To: 9front@9front.org Precedence: bulk One potential other solution for wloc: don't use the full label, but only the first token, which is likely a command without arguments. This would fix the rc pid issue and still work the same as always. Of course you lose the ability to reconstruct your programs with arguments (e. g. filenames). sirjofri