From: Clint Adams <clint@zsh.org>
To: Wayne Davison <wayned@users.sourceforge.net>
Cc: zsh-workers@sunsite.dk
Subject: Re: Another idea on how to insert illegal multibyte characters
Date: Thu, 12 Jan 2006 20:00:15 -0500 [thread overview]
Message-ID: <20060113010015.GA2435@scowler.net> (raw)
In-Reply-To: <20060112034200.GB28221@dot.blorf.net>
> I created an initial patch for this. It works to insert the necessary
> letters into the command-line, but has a bug where tab completion will
> not remove enough characters when moving from match to match if the
> previous match had one or more expanded $'\321' sequences. If folks
> like this idea, I imagine this bug wouldn't be too hard to fix.
Sounds better than the status quo.
prev parent reply other threads:[~2006-01-13 1:00 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
2006-01-13 1:00 ` Clint Adams [this message]
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=20060113010015.GA2435@scowler.net \
--to=clint@zsh.org \
--cc=wayned@users.sourceforge.net \
--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).