From: Wayne Davison <wayned@users.sourceforge.net>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: (F) note
Date: Mon, 5 Apr 2004 09:07:51 -0700 [thread overview]
Message-ID: <20040405160751.GB6805@blorf.net> (raw)
In-Reply-To: <12254.1081171579@csr.com>
On Mon, Apr 05, 2004 at 02:26:19PM +0100, Peter Stephenson wrote:
> +`full' (i.e. non-empty) directories. Note that the
> +opposite sense tt(LPAR()^F)tt(RPAR()) gives files which are
> +either empty, or not directories. Use tt(LPAR()/^F)tt(RPAR()) for
> +empty directories
This sentence makes it sound like zsh is checking for zero-length files.
How about this wording:
... Note that the
opposite sense tt(LPAR()^F)tt(RPAR()) results in both
empty directories and non-directories. Use tt(LPAR()/^F)tt(RPAR())
for just empty directories.
..wayne..
prev parent reply other threads:[~2004-04-05 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 13:26 Peter Stephenson
2004-04-05 16:07 ` Wayne Davison [this message]
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=20040405160751.GB6805@blorf.net \
--to=wayned@users.sourceforge.net \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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).