From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Expanding quotes
Date: Tue, 24 Dec 2013 07:12:59 -0800 [thread overview]
Message-ID: <52B9A47B.7050009@eastlink.ca> (raw)
In-Reply-To: <131223111515.ZM31989@torch.brasslantern.com>
On 23/12/13 11:15 AM, Bart Schaefer wrote:
> and expect completion to *supply* the missing backslash, because there
> is a file name ending with a quote. It gets even more complicated if
> the backslash is inside another set of quotes, etc. We spent quite a
> lot of time (years ago) responding to complaints about this kind of thing
> before finally concluding that we couldn't please everybody and should
> stick with making the common cases work.
Pardon for wandering off on a philosophical rant, but it seems to me
that there is a very deep error in even trying to solve 'problems' like
this. It is not logically possible to permit any syntax and still parse
a statement. All meaningful grammars exist--can only exist--because
they impose limitations on language. It is monstrous that a file name
is permitted to end with a quotation mark! Without reserved characters
we invite chaos. It's the same with spaces inside a filename--it is
insanity to permit it. And then the double quote is legal too?
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.
next prev parent reply other threads:[~2013-12-24 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 14:48 Yuri D'Elia
2013-12-17 18:26 ` Bart Schaefer
2013-12-23 17:38 ` Yuri D'Elia
2013-12-23 19:15 ` Bart Schaefer
2013-12-24 15:12 ` Ray Andrews [this message]
2013-12-24 16:24 ` Yuri D'Elia
2013-12-24 17:18 ` Ray Andrews
2013-12-26 14:50 ` Yuri D'Elia
2013-12-26 19:54 ` Ray Andrews
2013-12-24 16:11 ` Yuri D'Elia
2013-12-25 6:59 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B9A47B.7050009@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).