From: Peter Stephenson <pws@csr.com>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Another idea on how to insert illegal multibyte characters
Date: Mon, 13 Feb 2006 10:54:01 +0000 [thread overview]
Message-ID: <EXCHANGE03vAkb55hge0000c0bf@exchange03.csr.com> (raw)
In-Reply-To: <20060211101905.GA21506@dot.blorf.net>
Wayne Davison wrote:
> On Thu, Jan 12, 2006 at 09:23:19AM +0000, Peter Stephenson wrote:
> > The completion system is a bit more quoting aware: it knows whether or
> > not it needs to insert a backslash before special characters because of
> > quotes earlier on the line. Ideally it should handle unprintable
> > characters at the same point where it tries to do that. That doesn't
> > need to be done at the same time, though. (I would hope it could be
> > done independently and prevent the equivalent code inside zle kicking
> > in.)
>
> The attached patch is an alternative to my older patch that changed
> stringaszleline(). This one changes add_match_data(), which means that
> it is happening early enough that zsh could be made to figure out how
> to insert the $'\123' sequences into single- or double-quoted strings
> (though it does not yet do this). This patch also fixes the updating
> glitch that I mentioned my last patch had.
Any reasonably consistent attempt to do this, even if it's incomplete,
strikes me as a good thing. 4.3.1 isn't going to be completely
multibyte-aware anyway.
--
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
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
next prev parent reply other threads:[~2006-02-13 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 3:42 Wayne Davison
2006-01-12 9:23 ` Peter Stephenson
2006-02-11 10:19 ` Wayne Davison
2006-02-13 10:54 ` Peter Stephenson [this message]
2006-01-13 1:00 ` 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=EXCHANGE03vAkb55hge0000c0bf@exchange03.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).