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=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 15893 invoked from network); 25 Nov 2021 10:03:17 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 25 Nov 2021 10:03:17 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Thu Nov 25 04:57:51 -0500 2021 Message-ID: Date: Thu, 25 Nov 2021 10:57:41 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <0F86B9BF6BB00E5721AFCE94A8A6FECF@9lab.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: generic extended information injection just-in-time solution Subject: Re: [9front] [PATCH] rio: allow spaces in working directory path (-cd) when creating a new window Reply-To: 9front@9front.org Precedence: bulk yeah, wctl is ugly. probably is better to parse everything using gettokens(). as your patch doesnt handle quoting the quotes. the whole window command also will probably have issues with this kind of stuff... the quoting is definitely messed up in there. tho it is possible to quote from rc, like: fn q {a=$1 whatis a | sed 's!^a=!!;q'} or even get rid of wctl all together... it is a bit silly given you can just fork and mount $wsys yourself... then there are not two different code paths for creating a window. -- cinap