From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: spaces in filenames should be a crime.
Date: Tue, 28 Mar 2017 07:29:24 -0700 [thread overview]
Message-ID: <ee8d03d9-be65-9177-04e8-99fa05756257@eastlink.ca> (raw)
In-Reply-To: <60a213ad-6cb3-bef4-9e61-f2c1611a5e71@gmx.de>
On 28/03/17 02:08 AM, Martin Richter wrote:
echo $(**/*(.om[1])
> I think you are after
>
> $ print -- **/*(.Nom[1])
>
Ha! You know I was actually speculating, that wasn't supposed to work
even remotely, yet I see it was not far from reality -- zsh can and does
make a list of the files, it does not only do it when 'helping' ls or
some other binary. So ls is merely supplying extra information about
the files as may be desired, it does not 'make' the list of files.
That's residual DOSthink again -- ok the shell globs the filenames, but
only 'with' ls, that is, ls 'asks' zsh to expand a list of files. NO!
zsh creates the list all by itself ls or no ls. ls is a passive
recipient, there is no 'request'. Yes?
next prev parent reply other threads:[~2017-03-28 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 20:22 Ray Andrews
2017-03-26 20:57 ` Vadim A. Misbakh-Soloviov
2017-03-26 21:18 ` Daniel Shahaf
2017-03-26 22:41 ` Ray Andrews
2017-03-26 23:20 ` Bart Schaefer
2017-03-27 0:47 ` Ray Andrews
2017-03-27 1:11 ` Chris ccb
2017-03-27 1:45 ` Ray Andrews
2017-03-27 1:44 ` Martijn Dekker
2017-03-27 2:17 ` Ray Andrews
2017-03-27 18:53 ` Jesper Nygårds
2017-03-27 23:18 ` Mikael Magnusson
2017-03-28 0:46 ` Ray Andrews
2017-03-28 9:08 ` Martin Richter
2017-03-28 14:29 ` Ray Andrews [this message]
2017-03-28 16:10 ` Daniel Shahaf
2017-03-28 18:01 ` Ray Andrews
2017-03-28 18:38 ` Martijn Dekker
[not found] ` <60a213ad-6cb3-bef4-9e61-f2c1611a5e71__30788.3357666016$1490694707$gmane$org@gmx.de>
2017-03-29 11:27 ` Stephane Chazelas
2017-03-29 14:50 ` Ray Andrews
2017-03-29 15:21 ` Peter Stephenson
2017-03-29 16:21 ` Ray Andrews
2017-03-30 17:36 ` Bart Schaefer
2017-03-28 16:42 ` Matthew Martin
2017-03-26 21:24 ` Peter Stephenson
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=ee8d03d9-be65-9177-04e8-99fa05756257@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).