From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Expanding quotes
Date: Thu, 26 Dec 2013 11:54:37 -0800 [thread overview]
Message-ID: <52BC897D.7040606@eastlink.ca> (raw)
In-Reply-To: <l9hfmu$69n$1@ger.gmane.org>
On 26/12/13 06:50 AM, Yuri D'Elia wrote:
> On 12/24/2013 06:18 PM, Ray Andrews wrote:
>> 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.
> I think you're conflating the text UI of a shell, the filesystem and the
> shell language itself as part of the same issue. Yes, taken together, I
> do agree that from my user point of view it's definitely inconvenient
> and the interaction is not ideal. However, I would gladly prefer a shell
> solution than "fixing" what's clearly not broken: the filesystem.
You're right, I'm looking at this as one collective issue. But IMHO the
thing that is broken is to permit things like double quotes in a
filename at all. From what I understand, POSIX does not allow it, but
maybe I misunderstand. Anyway, if somehow zsh can learn to live with
this sort of thing, then so be it, but I think the task should not be
asked. Perhaps some switch or flag of some sort could be added to
indicate: "I have quotes in filenames here ... God be with you." Anyway,
that's how it looks to me, maybe I'm wrong.
next prev parent reply other threads:[~2013-12-26 20:24 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
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 [this message]
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=52BC897D.7040606@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).