From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18127 invoked by alias); 24 Dec 2013 17:48:55 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18251 Received: (qmail 4836 invoked from network); 24 Dec 2013 17:48:38 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Authority-Analysis: v=2.1 cv=HYUtEE08 c=1 sm=1 tr=0 a=Rg+YtRPeu5VacD9nNCCenQ==:117 a=Rg+YtRPeu5VacD9nNCCenQ==:17 a=0y6Rm8g2FWsA:10 a=8nJEP1OIZ-IA:10 a=og8RhBKwAX4A:10 a=QbMrfowzap4P9rcY6GcA:9 a=wPNLvfGTeEIA:10 Message-id: <52B9C1E9.2050000@eastlink.ca> Date: Tue, 24 Dec 2013 09:18:33 -0800 From: Ray Andrews User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-version: 1.0 To: zsh-users@zsh.org Subject: Re: Expanding quotes References: <131217102648.ZM8656@torch.brasslantern.com> <131223111515.ZM31989@torch.brasslantern.com> <52B9A47B.7050009@eastlink.ca> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit On 24/12/13 08:24 AM, Yuri D'Elia wrote: > On 12/24/2013 04:12 PM, Ray Andrews wrote: >> file name .................. two identifiers so ... >> "file name" .................. is the filename ... << file name >> or >> are the double quotes include in the filename so that the filename is >> .... << "file name" >> ? >> >> Madness! >> >> Granted I'm still a relative beginner, but it seems to me that the >> syntax of zsh (all sh*) is already vastly over complicated, even >> Byzantine. As more and more special situations are handled, the code >> must mushroom into an intractable mess, and actually create more >> problems than it solves. Better IMHO not to even try. > Quoting is invariably part of any language construct. Of course. > It's really important, especially as a beginner, to understand quoting > right from the start as a "normal event", not as an exception. Of course. > Restricting the allowed characters of a file in the file system will not > remove quoting issues of a variable's value (for example). > > To wrap your mind against it, you might see quoting as a problem for the > interpreter to *separate arguments* and not to interpret data. That is, > if we could choose # as an argument separator, we could have any > character in the file name except #. It just so happens that it's > /usually/ more readable to type: That's just the point: There must be reserved characters, and it seems to me that quotation marks are first on that list. Also, as a policy, I prefer simplicity with some resulting limitations on what can be done, over complicated efforts to do 'anything'. It's just as Bart said, some issues are better left 'unsolved'. The solution could be worse than the problem. I think back to my DOS days, where almost all of the 'special' characters were reserved--it sure made things simpler. > $ command argument "a value" > > then > > $ command#argument#a value > > Just my 2c. > And mine ;-) I come at this, not as a zsh expert, but as a guy who knows something about information theory. Noam Chomsky would have something to say about this sort of issue. >