From: Clint Adams <schizo@debian.org>
To: zsh-workers@sunsite.dk, "Benjamin Hill (Mako)" <mako@debian.org>,
289442-forwarded@bugs.debian.org
Subject: Re: Bug#289442: zsh: completions do not respect LC_COLLATE
Date: Sun, 9 Jan 2005 10:35:43 -0500 [thread overview]
Message-ID: <20050109153543.GA7922@scowler.net> (raw)
In-Reply-To: <E1CnUVX-0005Di-00@nozomi>
> Thanks for maintaining zsh Clint!
>
> AFAICT, results returned by tab completions to do not respect
> LC_COLLATE. Preferabley, zsh should sort completions according to
> whatever LC_COLLATE is set to at the time the completions are
> presented.
>
> To reproduce the bug, go into a directory with upper case and
> lowercase filenames. Set LC_COLLATE to C or POSIX and you should see
> case sensative sorting for a command like ls and in the completions of
> the ls command. Now set LC_COLLATE to, for example, en_US.UTF-8 which
> sorts case insensatively. The behavior will be changed for ls but not
> for tab completions of ls from within zsh.
>
> Invoking zsh with the LC_COLLATE set does not alter this behavior.
There were some concerns with locale-specific collation order in the
past with respect to surprise data loss when globbing.
http://www.zsh.org/mla/users/1998/msg00740.html
http://www.zsh.org/mla/workers/1999/msg02226.html
However, the real issue with your sorting problem seems to be the use of
a comparison function that ignores locale and behaves differently
depending on the setting of the NUMERIC_GLOB_SORT option.
I think we could change the character comparison at the end of
setbpcmp() to a strcoll(), or do setxfrm()'s at the beginning.
next parent reply other threads:[~2005-01-09 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CnUVX-0005Di-00@nozomi>
2005-01-09 15:35 ` Clint Adams [this message]
2005-01-09 16:12 ` Clint Adams
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=20050109153543.GA7922@scowler.net \
--to=schizo@debian.org \
--cc=289442-forwarded@bugs.debian.org \
--cc=mako@debian.org \
--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).