From: "Joël Porquet" <joel@porquet.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>,
"zsh-workers" <zsh-workers@zsh.org>
Subject: Re: Bug in 5.2 version with the key ²
Date: Mon, 14 Dec 2015 17:11:59 +0100 [thread overview]
Message-ID: <1450109519.400120.467043193.71EB1317@webmail.messagingengine.com> (raw)
In-Reply-To: <615807418.207235.1450108735625.JavaMail.open-xchange@oxbe7.tb.ukmail.iss.as9143.net>
Awesome,
I will wait for the next version then!
Thanks a lot,
Joël
On Mon, Dec 14, 2015, at 04:58 PM, Peter Stephenson wrote:
> > Anyway, since 5.2, this doesn't work anymore. Whenever I hit the ² key,
> > instead of looping through the possible completion possibilities, it
> > displays several interrogation points:
>
> Thanks, we just fixed this in the code a week or so ago.
>
> pws
prev parent reply other threads:[~2015-12-14 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 15:24 Joël Porquet
2015-12-14 15:58 ` Peter Stephenson
2015-12-14 16:11 ` Joël Porquet [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=1450109519.400120.467043193.71EB1317@webmail.messagingengine.com \
--to=joel@porquet.org \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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).