zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Some groundwork for Unicode in Zle
Date: Fri, 14 Jan 2005 13:10:35 +0000	[thread overview]
Message-ID: <200501141310.j0EDAZj7014813@news01.csr.com> (raw)
In-Reply-To: <200501111359.j0BDxbQn001884@news01.csr.com>

I have committed the patch to lay some groundwork for Unicode, and
updated the version in the archive to 4.2.3-dev-1.

To recap, I'm hoping it will be possible to change the zle line
variable, now zleline, to use wchar_t, while keeping a multibyte string
in the main shell, and probably completion for now (since completion
interacts with the main shell).  Any relaxing of assumptions about the
environment can happen once this is basically working.

It should now be possible to locate all uses of the key zle variables
zleline, zlecs, zlell by name.  Earlier versions of the patch
incorrectly renamed other uses of ll and line.  I think I've caught all
these, but the completion code used a large number of internal variables
with the same names.

Trapping and converting all direct or indirect uses of zlecs (cursor
position) and zlell (line length) outside the core zle code to use the
correct position with a multibyte string is likely to be a nightmare.

-- 
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.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  parent reply	other threads:[~2005-01-14 13:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 13:52 Peter Stephenson
2005-01-11 13:59 ` Peter Stephenson
2005-01-11 15:11   ` DervishD
2005-01-14 13:10   ` Peter Stephenson [this message]
2005-01-15 17:35     ` Clint Adams
2005-01-15 19:28       ` Peter Stephenson
2005-01-17 10:59         ` NUL must be a first class citizen [was: Some groundwork for Unicode in Zle] Matthias B.
     [not found]           ` <msbREMOVE-THIS@winterdrache.de>
2005-01-17 11:19             ` Peter Stephenson
2005-01-11 14:51 ` Some groundwork for Unicode in Zle Oliver Kiddle
2005-01-11 14:54   ` Mads Martin Joergensen
2005-01-11 14:56     ` Mads Martin Joergensen
2005-01-11 15:30   ` Peter Stephenson
2005-01-11 16:31     ` Bart Schaefer
2005-01-11 15:09 ` DervishD
2005-01-11 16:27 ` Bart Schaefer
2005-01-11 16:35   ` Vin Shelton
2005-01-11 16:49   ` DervishD
2005-01-14 15:54 François-Xavier Coudert
2005-01-14 16:06 ` Clint Adams
2005-01-14 16:20   ` François-Xavier Coudert
2005-01-14 16:49 ` 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=200501141310.j0EDAZj7014813@news01.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).