From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>,
zsh-workers@math.gatech.edu (Zsh hacking and development)
Subject: Re: 'LC_COLLATE=de ls [A-Z]*' expands to 'every file' including lowercase
Date: Wed, 8 Jul 1998 04:02:12 -0700 [thread overview]
Message-ID: <980708040212.ZM8132@candle.brasslantern.com> (raw)
In-Reply-To: <199807080640.BAA01227@hzoli.home>
On Jul 8, 1:40am, Zoltan Hidvegi wrote:
} Subject: Re: 'LC_COLLATE=de ls [A-Z]*' expands to 'every file' including l
}
} > I'd vote in favor of removing HAVE_STRCOLL from matchonce() in glob.c.
}
} According to the standard:
}
} LC_COLLATE
} This variable determines the behaviour of range expressions,
} equivalence classes and multi-character collating elements
} within pattern matching.
Which standard, specifically?
This is a case where that standard is harmfully flying in the face of
common sense. Of course LC_COLLATE ought to apply to POSIX character
classes once those are supported, and ought to apply to the collation
of any resulting ordered list. But to have it apply to the characters
within ranges like [A-Z] will cause the simplest shell scripts to go
completely haywire; we'll have to start putting "local LC_COLLATE=C"
or some such at the top of every autoloaded function, along with all
the "emulate -R" and "setopt localoptions" junk that's already there.
Standards are not meant to be followed blindly. That's why the IETF,
for example, has a collection of rules for interpreting MUST, SHOULD,
MAY, etc. when they appear in IETF documents.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1998-07-08 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-06 17:28 C. v. Stuckrad
1998-07-06 18:14 ` Bart Schaefer
1998-07-07 15:30 ` C. v. Stuckrad
1998-07-08 6:40 ` Zoltan Hidvegi
1998-07-08 11:02 ` Bart Schaefer [this message]
1998-07-08 15:36 ` Zoltan Hidvegi
1998-07-08 17:24 ` Bart Schaefer
1998-07-08 19:35 ` Zoltan Hidvegi
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=980708040212.ZM8132@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=hzoli@cs.elte.hu \
--cc=zsh-workers@math.gatech.edu \
/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).