From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: (N) defaults to whole directory listing
Date: Fri, 29 Jan 2021 09:01:07 -0800 [thread overview]
Message-ID: <7ea3f3f8-6aa9-bbab-40d7-2944b88e1709@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMp+JykOWEYQ5qO495-hOpQXh+4RN6iHcYTP-APg8XHESQ@mail.gmail.com>
On 2021-01-29 7:33 a.m., Roman Perepelitsa wrote:
>
> `ls` without arguments lists files in the current directory. This is
> mandated by POSIX and what everyone expects.
Of course.
>
> `no_such_file(N)` expands to nothing if there is no file named
> `no_such_file` in the current directory. This is in line with the zsh
> documentation and what everyone expects.
That's about what I I expected to hear. zsh can't be expected to feed
'ls' with something that duplicates a non-existent file, it can only
remove the non-existent file thus leaving no argument thus ls must be
'ls *'. I had thought there might be some hidden mechanism by which ls
might be informed that the given argument fails but I can quite
understand that no such thing exists -- zsh just removes the
non-existent argument and that's all she can do and ls is on it's own.
Thanks Roman.
next prev parent reply other threads:[~2021-01-29 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 15:24 Ray Andrews
2021-01-29 15:33 ` Roman Perepelitsa
2021-01-29 17:01 ` Ray Andrews [this message]
2021-01-29 17:52 ` Lawrence Velázquez
2021-01-29 19:52 ` Ray Andrews
2021-01-29 18:47 ` Bart Schaefer
2021-01-29 19:04 ` Bart Schaefer
2021-01-30 10:50 ` Roman Perepelitsa
2021-01-30 15:00 ` Beverly Pope
2021-06-18 10:24 ` Why does >&- produce an error message when connected to a builtin? (was Re: (N) defaults to whole directory listing) Marlon Richert
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=7ea3f3f8-6aa9-bbab-40d7-2944b88e1709@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).