From: Zefram <zefram@dcs.warwick.ac.uk>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: autoparamkeys broken in 3.1.1
Date: Mon, 10 Feb 1997 11:39:15 +0000 (GMT) [thread overview]
Message-ID: <20103.199702101139@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199702101057.LAA15679@hydra.ifh.de> from "Peter Stephenson" at Feb 10, 97 11:57:20 am
Peter Stephenson wrote:
>% zsh -f
>% setopt autoparamkeys
>% echo $pat<TAB> -> echo $path _ # now type [
>% echo $path [
> ^ stays here, should spring back to end of $path
>% echo ${path<TAB> -> echo ${path _ # now type }
>% echo ${path }
> ^ ditto.
With straight 3.1.1, these work for me.
-zefram
next prev parent reply other threads:[~1997-02-10 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-10 10:57 Peter Stephenson
1997-02-10 11:39 ` Zefram [this message]
1997-02-10 14:48 ` Peter Stephenson
1997-02-10 15:02 ` Zefram
1997-02-10 16:36 ` 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=20103.199702101139@stone.dcs.warwick.ac.uk \
--to=zefram@dcs.warwick.ac.uk \
--cc=pws@ifh.de \
--cc=zsh-workers@math.gatech.edu \
/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).