From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: Btw.: glob-qualifier
Date: Mon, 1 Feb 1999 09:21:37 +0100 (MET) [thread overview]
Message-ID: <199902010821.JAA02870@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 29 Jan 1999 09:31:43 -0800
Bart Schaefer wrote:
> On Jan 29, 2:37pm, Sven Wischnowsky wrote:
> } Subject: PATCH: Re: Btw.: glob-qualifier
> }
> } > [...] (o(ug=w,o+r)) for "user and group must have exactly the write
> } > bit set, and other must have at least r" and (o(u+x,go-w)) for "user
> } > must have at least the execute bit set, and group and other must not
> } > have write" and so on.
> }
> } The patch below implements this (with a few extras).
>
> Nifty! Now I only have one question ... is there another, better letter
> than `o' that could be adopted (since the mode is no longer `o'ctal),
> thus giving us both o and O for ascending/descending sorts, as in the
> parameter flags?
(...and print.) Yes, I wanted to do it in exactly this way, when I
discovered the old `o' modifier. I also thought about altering the
name of the `o' modifier.
This would also reverse the meaning of the `O' qualifier.
But since `o' wasn't documented and `O' is new, it hopefully wouldn't
cause too much trouble.
> (I'd ask about this on zsh-users first, though, just in case anybody is
> making some important use of the old undocumented `o'.)
Ok.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-02-01 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-01 8:21 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-03 11:06 Sven Wischnowsky
1999-01-29 13:37 Sven Wischnowsky
1999-01-29 17:31 ` Bart Schaefer
1999-01-29 8:39 Sven Wischnowsky
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=199902010821.JAA02870@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).