zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: various weirdnesses with unicode support
Date: Fri, 9 Sep 2005 12:53:41 +0100	[thread overview]
Message-ID: <20050909125341.12a21423.pws@csr.com> (raw)
In-Reply-To: <237967ef0509080731646f7306@mail.gmail.com>

Mikael Magnusson <mikachu@gmail.com> wrote:
> > > > > * Having zsh in utf-8 locale but the terminal inputting for example
> > > > > ISO-8859-1 makes zsh enter some weird state where
>
> > For example, this patch uses the existing $KEYTIMEOUT variable to time out
> > the remaining bytes of a multibyte character.  If mbrtowc() reported
> > there was more, but reading the next byte took more than $KEYTIMEOUT
> > hundredths of a second, the character is returned as a wide '?' and
> > the shift state for character input is reset.
> > 
> > Much of the patch is adding the extra argument to getbyte to differentiate
> > a real EOF from a timeout.
> > 
> > Does this help?  I suspect we probably need something like this anyway.
> 
> It seems to help a bit. If i press å (a with a ring), and then press a
> a few times, zle still seems to be in a mostly normal state. But if i
> press several å in a row i can't seem to get out.

I've checked this in anyway, with some slight tweaks: the MB state is
also reset if getrestchar() returns EOF, and I've added zle documentation
indicating that $KEYTIMEOUT is applied to multibyte characters.

I won't be much use with debugging this since I have currently no way
of generating invalid characters.  X Windows is smart enough to convert
between windows.  There may be some way of confusing it with the locale
or character set.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************


  reply	other threads:[~2005-09-09 11:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 20:30 Mikael Magnusson
2005-09-08  8:55 ` David Gómez
2005-09-08 10:02   ` Peter Stephenson
2005-09-08 10:32     ` Peter Stephenson
2005-09-08 14:31       ` Mikael Magnusson
2005-09-09 11:53         ` Peter Stephenson [this message]
2005-09-09 12:33           ` Mikael Magnusson
2005-09-09 16:52             ` Peter Stephenson
2005-09-09 16:56               ` David Gómez
2005-09-09 12:29 ` Mikael Magnusson
2005-09-09 13:44   ` Peter Stephenson
2005-09-09 20:32 ` Peter Stephenson
2005-09-09 20:40   ` 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=20050909125341.12a21423.pws@csr.com \
    --to=pws@csr.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).