zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: crash in completing code with unicode support
Date: Tue, 16 Aug 2005 14:01:50 +0200	[thread overview]
Message-ID: <237967ef050816050130fefbf8@mail.gmail.com> (raw)
In-Reply-To: <200508161157.59407.arvidjaar@newmail.ru>

On 8/16/05, Andrey Borzenkov <arvidjaar@newmail.ru> wrote:
> On Tuesday 16 August 2005 05:37, Mikael Magnusson wrote:
> > I tried the recent developments with unicode support, and it's going
> > pretty well. I can write text in zle without it showing up as
> > ^{saa'*^+{^ instaed of actual text. Backspacing over doublewidth
> > characters only steps back one cell, but i understand this has not
> > been worked on yet.
> 
> this works for me using UTF-8 Russian. Backward word has problems but backword
> char works. Or do you mean, characters with double display width? I am not
> aware of these in European languages?

No, they are single display width. Your russion character works fine
for me too, only crashes with the characters i listed.

> > One problem i have encountered though, is if i
> > have a couple file that starts with the same multibyte character (it
> > seems to be important that it is at the very beginning of the name),
> > and then different endings, zsh crashes when i try to tabcomplete
> > them. An obvious case where this happens is tabcompleting mp3 files
> > where the artist's name starts with Ø (a danish capital O with a /
> > through it, any of åäöæøÅÄÖÆØ seems to do the same thing too).
> 
> Does not crash here but looks pretty weird:
> 
> {pts/1}% pkg/bin/zsh -f
> localhost% cd tmp/foo
> localhost% autoload -U compinit; compinit
> localhost% la Ф
> \M-P\M-$1  \M-P\M-$2
> localhost% ls
> Ф1  Ф2
> 
> When I continue to complete it inserts correct string in command line so it is
> just listing that is wrong.
> 
> Using complist/menuselect works just nicely. Could you please try to reproduce
> it using zsh -f with the smallest set of extra options. And please, show
> UTF-8 (or UNICDOE) representation of characters that crash zsh and yuor OS
> and locale settings.

This should create the files i have,

mkdir /tmp/foo
cd /tmp/foo
a=`echo +ANg- | iconv -f utf-7 -t utf-8`
touch ${a}a ${a}b
zsh -f
autoload -U compinit; compinit
ls <tab><tab>

That is all i have to do to get the crash. (I didn't compile with
--enable-zsh-debug, because then i only get an error message like
"BUG: substring ends in the middle of a metachar in ztrsub()", instead
i specified the flags manually)

> -andrey

-- 
Mikael Magnusson

  parent reply	other threads:[~2005-08-16 12:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  1:37 Mikael Magnusson
2005-08-16  7:57 ` Andrey Borzenkov
2005-08-16 11:44   ` Clint Adams
2005-08-16 12:09     ` Nikolai Weibull
2005-08-16 16:16       ` Andrey Borzenkov
2005-08-18  9:34         ` Peter Stephenson
2005-08-16 12:01   ` Mikael Magnusson [this message]
2005-08-16 19:27     ` Andrey Borzenkov
2005-08-16 21:37       ` Wayne Davison
2005-08-16 21:49         ` Wayne Davison
2005-08-17  0:22           ` crash fixed, other minor issue though was: " Mikael Magnusson
2005-08-18 16:48             ` Andrey Borzenkov
2005-08-18 16:35           ` Andrey Borzenkov

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=237967ef050816050130fefbf8@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).