zsh-workers
 help / color / mirror / code / Atom feed
From: "Mikael Magnusson" <mikachu@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Directories with multibyte names are never empty
Date: Wed, 4 Jun 2008 14:12:23 +0200	[thread overview]
Message-ID: <237967ef0806040512s540921f9s3b5c0d1f9fba3216@mail.gmail.com> (raw)
In-Reply-To: <20080604140146.77f2ab35@DervishD>

2008/6/4 Raúl Núñez de Arenas Coronado <raul@dervishd.net>:
> Hi all :)
>
> First of all, my excuses if this is already solved. I haven't been
> following the list with much attention lately and I'm using zsh-4.3.4
> in my Ubuntu, which may be a bit outdated.
>
> This said, the problem is very easy to reproduce:
>
> $ mkdir H
> $ mkdir H/ō  <-- This is an "o" with a dash above
> $ mkdir H/a
> $ mkdir H/empty
> $ touch H/a/test
> $ touch H/ō/test
> $ print -l **/*(/^F)
> H/empty
> H/ō
>
> The last output should be just "H/empty", but the directory with the
> "ō" is considered empty, too (and it is obviously not empty).
>
> I have multibyte enabled and my encoding is UTF-8 (both in console and
> in the filesystem). Curiously, this doesn't happen with letters like
> "ñ", "á", "é", etc. which are multibyte and are encoded using two
> bytes in UTF-8, just like "ō" (0x014D => 0xC5 0x8D in UTF-8).
>
> My locale is a mix between en_US-UTF-8 and es_ES-UTF-8 (I want the
> messages in English; date, time, collation and ctype in Spanish).
>
> If you need more information, just tell. Thanks a lot in advance :)

FWIW, it works fine here, 4.3.6-dev-0.

-- 
Mikael Magnusson

  reply	other threads:[~2008-06-04 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 12:01 Raúl Núñez de Arenas Coronado
2008-06-04 12:12 ` Mikael Magnusson [this message]
2008-06-04 12:36 ` Peter Stephenson
2008-06-04 13:21   ` Raúl Núñez de Arenas Coronado

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=237967ef0806040512s540921f9s3b5c0d1f9fba3216@mail.gmail.com \
    --to=mikachu@gmail.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).