From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) by hurricane.the-brannons.com (Postfix) with ESMTPS id B694D21DE04 for ; Thu, 14 May 2015 12:15:12 -0700 (PDT) Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-02v.sys.comcast.net with comcast id TvF11q0042N9P4d01vFSr0; Thu, 14 May 2015 19:15:26 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-13v.sys.comcast.net with comcast id TvFR1q00P5LMg2101vFRUG; Thu, 14 May 2015 19:15:25 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <877fsbp3gu.fsf@mushroom.localdomain> User-Agent: edbrowse/3.5.4+ Date: Thu, 14 May 2015 15:15:25 -0400 Message-ID: <20150414151525.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=1431630926; bh=Krdnxo2kDK476GuXVhqzmZrnhu+o+mxZEWYBrWQmOWI=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=aHGElZFvAP6zwOlVvltLxoFE4hN8B94ZLAFUg4GtWtyp18freGqP++3VrYBUf5uUD myZ8aokWX+9T/zuwJSaKglRsSUQQNdpgIAAllV0yfPvLWGoe9kseOXdz8DVnjeMyAg 3m11CMIwA7XQq7JJTjBfHic0+EZolpCZiAEao5fQU84E94deKbsy1+DFTdcPh5+rk7 khxKr0b8y9QYrr4MgOkY9NAWr1t6l8vcWU3yNDf+HF/oukvyzOeCmmJUkP0i5Ta3+y 4ORG0VBtvqGmYNKicMch+8kd7JsxDYxSjWfueQXI9fPIhEi0OvPZl3VufITxV46oNy c8CGHRk1sAm+g== Subject: [Edbrowse-dev] we shouldn't be letting glob() do our tilde expansion 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: Thu, 14 May 2015 19:15:12 -0000 > lacks GLOB_TILDE_CHECK (and GLOB_TILDE for that matter). Yeah that's a concern. > The insurmountable one is that it creates a big inconsistency Well it's sort of an inconsistency and sort of not. If you expand foo*bar and there is no match it remains foo*bar. If you expand ~/foo and there is no match it remains ~/foo. That is consistent, and how glob works, but it might not be how you want it to work. In your defense, the shell expands as you want edbrowse to, expanding ~ first and then doing the glob. We can roll our own ~ expansion, It wouldn't be hard. I suppose using the getpwent routines and looking for login match and pasting in the home directory, I think that's what glob does for us, and I really didn't want to have to do it myself, but whatever. Let me think about this one for a bit while I finish the code compression project, which is coming along nicely. Karl Dahlke