From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 725117AE83 for ; Fri, 17 Apr 2015 06:34:15 -0700 (PDT) Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-08v.sys.comcast.net with comcast id H1Yu1q0042PT3Qt011ZBr0; Fri, 17 Apr 2015 13:33:11 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-14v.sys.comcast.net with comcast id H1ZB1q00A5LMg21011ZBWC; Fri, 17 Apr 2015 13:33:11 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20150316174053.eklhad@comcast.net> <20150417125002.GA14517@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.3+ Date: Fri, 17 Apr 2015 09:33:11 -0400 Message-ID: <20150317093311.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=1429277591; bh=56e4H+ovfvmf02KQHupe7RD0MCBLr/nKWzAaS8fkEug=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=PtKr1VfP7vbnBCKlKF6Esnghbw4bkLxh/ina0MRoVJIU3shipM6eTZrJyLnYRup+E JzFGpz+dw8Nyh4g0yUS/mPhyQz9ekBVaOE++E/PuI45lfnbQRIDOQVBCVfFyFQ8Bi+ L4+JlubmKSKjl0rVcQz4STicVfqnCv9DtIyq1bSzWaiqDP5Aw9Au2StKqePw7sEXod 9q3bOH5DU6reyEq9oCPK+rekGMmfeUSE8OVcEGcVG6GHcNdj0WEVmQ5evv9HPokNLa C5Y6tqNGcVaudpwQE9fBFDtQT0hl4RcQCigLaqyXqfd/wZ1FMVwM/cdokI6OPJuP4h LX4DEVtv9KhyQ== Subject: [Edbrowse-dev] wordexp again 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: Fri, 17 Apr 2015 13:34:16 -0000 > Basically the "quick check" in envFile is just wrong and needs to go since it And yet, I feel like this check was doing something from the user's perspective. Like maybe edbrowse only tries to expand a filename through the shell if you really intended that it do that. So it wouldn't try to expand just because the file had a parenthesis or some such. Maybe that doesn't matter IDK. And is this really involved at all in the directory backslash bug that started this thread? Karl Dahlke