From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 0977D786FA for ; Sun, 28 Dec 2014 17:05:23 -0800 (PST) Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-04v.sys.comcast.net with comcast id ZD321p0032LrikM01D39xz; Mon, 29 Dec 2014 01:03:09 +0000 Received: from eklhad ([68.84.191.77]) by resomta-ch2-12v.sys.comcast.net with comcast id ZD391p0021gep3001D39ti; Mon, 29 Dec 2014 01:03:09 +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 20:03:09 -0500 Message-ID: <20141128200309.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=1419814989; bh=C3VQiLA+eAUxFZCYgwkc61J8RGAsBGe1Tk+/6/oGm3g=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=Iad8IwEcDhXff191WzILjiUXZ3RyoUucbYFhZ7UyxkcdPOui3hmZkeEpPP4P7zV2q 29+23/b5bRCDk5h1GDtNpLncjNgArNH/6pkmmM/fCxohLMk+V5KfSLvyggceqeC4Ew /K0PNJPR6LeIr3H7ejeqcvKB1OqbKKanAvMPjjrd/kqRxZ5Zck/lUctk3iSM0GJV5i HJpQziePvbo5mhGrsOQyz+0HLYovMCralr/va7ZHfYgHUDmwJz5ES2mMS/uUXmVTzU SwzIVIi5MLCeQkmfCNeS9BtgshXj6YtfPo1MK2uOpqA2KW94dF006Udr17ztlKuKNs r4b19mEhxEnIw== Subject: [Edbrowse-dev] glob 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: Mon, 29 Dec 2014 01:05:24 -0000 By using wordexp, Adam suggests > "posix shell" or words to that effect and then it becomes fairly clear Clear? Really? To you and me maybe. Bash does so many crazy things at the shell ... arithmetic, regexp substitution, and tries to interpret so many characters as something, I really don't want to go there. I should be able to call up a file called $phones/at&t without having to think about it. And no idea what a mac or windows user would think of all that complexity. What I have is generally liked, with no reported problems, though there may be some hidden bugs and some concerns. I like the idea of keeping my variable expansion, perhaps augmented with ${var} or $(var) (makefile style), and then call glob for the rest. Glob is the hard part anyways, and the potentially unportable part, so good to have a library do it. This expansion can be suspended individually by `` as in r ``* to read in the contents of a file called * Karl Dahlke