zsh-workers
 help / color / mirror / code / Atom feed
From: Danek Duvall <duvall@comfychair.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: multibyte FAQ
Date: Fri, 16 Dec 2005 01:39:49 -0800	[thread overview]
Message-ID: <20051216093949.GC21510@lorien.comfychair.org> (raw)
In-Reply-To: <200512142109.jBEL9S5v003595@pwslaptop.csr.com>

On Wed, Dec 14, 2005 at 09:09:28PM +0000, Peter Stephenson wrote:

> The disadvantage is that you can't input multibyte characters via the
> keyboard if they begin with the same meta sequence unless you bind the
> more specific sequence starting with that byte

Is there a simple way to find out which meta sequence block which multibyte
characters for people who aren't too familiar with UTF-8 encoding?

It might also be worth mentioning that, depending on your terminal
emulator, you might be able to sidestep the problem entirely.  In xterm at
least, you can control whether the meta key sets the eighth bit or sends an
escape character, depending on the values of the eightBitInput and
metaSendsEscape resources.  Other terminals may have similar setups.  There
may still be a certain set of people who won't get exactly what they want,
but it's probably pretty small.

Anyway, thanks for the explanation!

Danek


  reply	other threads:[~2005-12-16  9:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 18:31 Peter Stephenson
2005-12-14 18:41 ` Peter Stephenson
2005-12-15 14:42   ` Peter Stephenson
2005-12-14 19:25 ` [22076] " Danek Duvall
2005-12-14 21:09   ` Peter Stephenson
2005-12-16  9:39     ` Danek Duvall [this message]
2005-12-16 17:13       ` Bart Schaefer
2005-12-18 19:38         ` Danek Duvall
2005-12-18 21:10           ` Bart Schaefer
2005-12-18 14:14 ` PATCH: multibyte FAQ (MacOS X) Jun T.
2005-12-18 15:26   ` Andrey Borzenkov
2005-12-19  9:08     ` Jun T.
2005-12-18 19:41   ` Peter Stephenson
2005-12-21 16:15     ` 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=20051216093949.GC21510@lorien.comfychair.org \
    --to=duvall@comfychair.org \
    --cc=p.w.stephenson@ntlworld.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).