From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 0FD867AF0A for ; Fri, 17 Apr 2015 15:26:36 -0700 (PDT) Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-11v.sys.comcast.net with comcast id HARY1q0062LrikM01ARYKE; Fri, 17 Apr 2015 22:25:32 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-12v.sys.comcast.net with comcast id HARX1q00J5LMg2101ARY5x; Fri, 17 Apr 2015 22:25:32 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20150316174053.eklhad@comcast.net> <20150417215826.GF5949@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.3+ Date: Fri, 17 Apr 2015 18:25:31 -0400 Message-ID: <20150317182531.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=1429309532; bh=OJLsW8jq0K2mZZianUiAIt+Ke1ojvs3DXsyin+/1dzE=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=dQ4WiiTmRrCUqzAcit0Vac7mQFiVVTTGzOtMWyTKmcgGdOl6riZRC57qvUkRpjk7R f2f77Lg1xCXSoxYiDIZp0zd3zolUd8CW94bDvzRA1+4CzhIiCDA8Tv6kNELBu/HhOK dmN9/6rQ9gi5dW87JwmT/w4If84N9bHdQZDWEvhSwnrPECCIqGA5H4xRf3TQcHRZuN WJQ/daoY+txwaUMGAuo022k+l5YYjnnrE44G5xoY4BRjcejHDBVA1WHPXMj4aVFdv+ +3H5nKeiHsh3i+2kA6GiYWuCGbt0EkevyBgNfhdje4eIolD8uMhBX1jy0wSw5Fx3jq IMiUTns0BuAZA== 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 22:26:37 -0000 Reversing the sense of the leading ` is, I think, an interesting idea. There are no side effects unless you ask for them, and it would fix a bug that you introduced, wherein r5, to read the fifth buffer into the current buffer, no longer works. It doesn't work because 5 runs through wordexp and there is no file called 5. I use this feature a hundred times a day, to cut and paste text between sessions. Anyways it fails now because 5 runs through wordexp, but it use to work, and would work again if such lines did not go through wordexp by default, either because my syntax checker was back in place, or because you had to indicate so with a leading `. An unknown for me is how often I automatically, and without thinking, use * to edit or read a file; I just pattern match automatically, and I can see myself cursing and having to type it in again with a leading ` and by that time I probably could have just typed in the filename. Damn! and I'd be annoyed because here again it is different from the shell. I guess I'll have to sleep on this for a night or two, or maybe play with it in its different modes for a week or two, to get a sense of things. One thing I have to do right away is fix the r5 bug, in one way or another. Reading and writing among buffers just has to work for me. Karl Dahlke