zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: globbing bug, 3.0.6
Date: Fri, 28 Apr 2000 10:02:39 +0200 (MET DST)	[thread overview]
Message-ID: <200004280802.KAA20596@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 28 Apr 2000 01:01:53 +0000


Bart Schaefer wrote:

> On Apr 27,  3:11pm, Trond Eivind=?iso-8859-1?q?_Glomsr=F8d?= wrote:
> } Subject: Re: globbing bug, 3.0.6
> }
> } Chmouel Boudjnah <chmouel@mandrakesoft.com> writes:
> } 
> } > it's the POSIX standard behavior when locale setting is set.
> } 
> } And that's horribly broken IMHO. At least, I think it's broken in
> } shell expansion
> 
> I don't want to change this in 3.0.8 unless it's also changing in 3.1.7
> or soon thereafter.  What's the verdict on this one, folks?  Apparently
> bash behaves as zsh does now, but that's not a conclusive argument.

Right, and they get their own bug reports about this (for example on
gnu.bash.bug).


Andrej Borsenkow wrote:

> That's general question - how far is compatibility with current Unix
> standards important? For better or for worse - current behaviour is one
> of the requirements. The problem is (I can go into more details if
> needed) Zsh in current form does not and *can* not support full i18n as
> specified in docs (this applies to such obscure things as "collate
> elements" e.g.). So, the ultimate question is - should we aim at full
> POSIX/SUS/... compatibility, at least as an option (that may need
> substantial rewrite), or drop it in favour of more "user friendliness".
> 
> Now, with much more powerful regular expressions, I even agree - for
> interactive shell plain ASCII collating may be more appropriate - and
> scripts should use [[:class:]] form anyway.

I'd say we should add an option that turns on POSIX/i18n behaviour and 
defaults to `off' and documented like `currently this only
affects...'. I think its a case where not conforming to standards is
the right thing, reducing the number of (probably horrible)
surprises. Then we could think about adding the match-flags to turn
on/off the behaviour determined by the option for single patterns (I
haven't had a look at this match-flag code yet so I don't know how
hard to implement this is).

And later we can make the option control more things.

This also reminds me that the classes in match specs don't care about
the locale at all...

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-04-28  8:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-28  8:02 Sven Wischnowsky [this message]
2000-04-28  8:09 ` Andrej Borsenkow
  -- strict thread matches above, loose matches on Subject: below --
2000-04-28 11:24 Sven Wischnowsky
2000-04-18 14:45 Trond Eivind Glomsrød
2000-04-18 14:52 ` Zefram
2000-04-18 15:34   ` Trond Eivind Glomsrød
2000-04-18 18:44 ` Chmouel Boudjnah
2000-04-27 19:11   ` Trond Eivind Glomsrød
2000-04-28  1:01     ` Bart Schaefer
2000-04-28  5:42       ` Andrej Borsenkow
2000-04-28  9:06       ` Peter Stephenson

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=200004280802.KAA20596@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).