From: Beverly Pope <countryone77@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>,
Ray Andrews <rayandrews@eastlink.ca>,
Zsh Users <zsh-users@zsh.org>
Subject: Re: (N) defaults to whole directory listing
Date: Sat, 30 Jan 2021 09:00:23 -0600 [thread overview]
Message-ID: <0421713D-25C5-477A-90AD-C0BD2B40EED2@gmail.com> (raw)
In-Reply-To: <CAN=4vMop86hkyYMaBkF-tJaVRaN5Z28gJLqL9tSdy-uy1DNMgg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
> On Jan 30, 2021, at 4:50 AM, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
>
> On Fri, Jan 29, 2021 at 8:04 PM Bart Schaefer <schaefer@brasslantern.com <mailto:schaefer@brasslantern.com>> wrote:
>>
>> On Fri, Jan 29, 2021 at 7:33 AM Roman Perepelitsa
>> <roman.perepelitsa@gmail.com <mailto:roman.perepelitsa@gmail.com>> wrote:
>>>
>>> print -rC1 -- no_such_file(N)
>>>
>>> This will print `no_such_file` if such file exists and will do nothing
>>> otherwise.
>>
>> Not precisely nothing ... it will print a newline.
>
> If the file doesn't exist, the command is equivalent to this:
>
> print -rC1 --
>
> This command doesn't print anything.
% print -rC1 -- no_such_file(N)
zsh 5.8 (Ubuntu): prints nothing
zsh 5.7.1 (Mac): prints return
[-- Attachment #2: Type: text/html, Size: 6118 bytes --]
next prev parent reply other threads:[~2021-01-30 15: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
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 [this message]
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=0421713D-25C5-477A-90AD-C0BD2B40EED2@gmail.com \
--to=countryone77@gmail.com \
--cc=rayandrews@eastlink.ca \
--cc=roman.perepelitsa@gmail.com \
--cc=schaefer@brasslantern.com \
--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).