From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Cc: 419832-forwarded@bugs.debian.org, Alan Curry <pacman@TheWorld.com>
Subject: Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>
Date: Fri, 17 Aug 2007 07:55:15 -0700 [thread overview]
Message-ID: <070817075515.ZM26686@torch.brasslantern.com> (raw)
In-Reply-To: <20070817152210.6bb9559b@news01.csr.com>
On Aug 17, 3:22pm, Peter Stephenson wrote:
} Subject: Re: Bug#419832: zsh: expanding non-ASCII filenames with <TAB>
}
} On Fri, 17 Aug 2007 08:08:44 -0400
} Clint Adams <schizo@debian.org> wrote:
} > What's worse is that if you `touch a b$'\300' c` in an empty directory,
} > cat *<TAB> will only expand to "a b".
}
} I can believe there's some logic missing here, but it's not currently
} clear to me here what. Could you post an explicit recipe for
} getting from an unconfigured shell to an expansion that doesn't
} (somehow) display all the elements?
This is a problem with old compctl, not compsys.
With compinit run and LANG=C and/or "unset LANG" I get:
schaefer<504> cat *<TAB>
schaefer<504> cat a
Completing expansions
a b$'\300' c
Completing all expansions
a b$'\300' c
Completing original
*
With LANG=en_US I get:
schaefer<506> cat *<TAB>
schaefer<506> cat a
Completing expansions
a bÀ c
Completing all expansions
a bÀ c
Completing original
*
With "compsys" turned off (old compctl completion) I get the something
sensible when LANG=en_US:
torch% cat *<TAB>
torch% cat a bÀ c
But the bug appears with LANG unset:
torch% cat*<TAB>
torch% cat a b
So the recipe PWS wants is just to run "zsh -f".
next prev parent reply other threads:[~2007-08-17 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070817001222.GA19399@scowler.net>
[not found] ` <200708170905.l7H9521T1534406@shell01.TheWorld.com>
2007-08-17 12:08 ` Clint Adams
2007-08-17 14:22 ` Peter Stephenson
2007-08-17 14:55 ` Bart Schaefer [this message]
2007-08-20 21:18 ` Peter Stephenson
2007-08-18 4:29 ` 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=070817075515.ZM26686@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=419832-forwarded@bugs.debian.org \
--cc=pacman@TheWorld.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).