From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 11C3178949 for ; Sun, 28 Dec 2014 11:11:34 -0800 (PST) Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-12v.sys.comcast.net with comcast id Z79E1p0062JGN3p0179KaM; Sun, 28 Dec 2014 19:09:19 +0000 Received: from eklhad ([68.84.191.77]) by resomta-ch2-10v.sys.comcast.net with comcast id Z79K1p00D1gep300179KVF; Sun, 28 Dec 2014 19:09:19 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.2 Date: Sun, 28 Dec 2014 14:09:19 -0500 Message-ID: <20141128140919.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419793759; bh=nr9nmZTtS+yC6PrCW7NyvyiByQGzA7Ie+qQa48zPjXg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=hfexo2Kg4KYCnYgfV4cuaoLEmopANsNkNiVHmMtGUXwgAd1w3nAfJWNkVmxda/maO mxYAooekkLYdDWc8t0DW/c4Si+ljdqS/op44ENnM1LQAVAdLK/zn/YjGvNVZR80jfD 4O1NYQfxJoyHxUhxebZ5VrQaV5TwEH/tPAr0g3d8NgaRJEpBF9LZchTgfMwSj+/jTe dTwCAd0jLAU7W4IRknWIKn4WxLSMSpBE11k0/ptaeOL00BlF/wBdCe3lGTiPZULh/0 xr3x9zcV7EcQzXpGyzQTLO/SsI9irfNf+Oi2gumBdM7WuuBl20j1RD7zmYbPbhnNy1 UACnj6r/aKnAQ== Subject: [Edbrowse-dev] glob, wordexp X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2014 19:11:34 -0000 Edbrowse has the feature that you can read or write files using shell variables and even wildcard expansion, if the result is one file. I use this feature all the time! r ~/work/whatever/st*k.c w $backup/12-25-14.c and things like that. Most of this is done by envFile() in stringfile.c, which is 200 lines of rather awkward code. I would like to replace most of this with a call to glob or wordexp. This leverages existing libraries, and is more portable, since someone else is reading through subdirectories etc. Are there any reasons I should or should not do this, or any thoughts on this? I know glob does too little, it doesn't expand shell variables, but wordexp may do too much, like all the fancy things bash does to a line. I need to see how much I can control it with flags. Karl Dahlke