Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PROMPT_SUBST bug?? zsh-2.6-beta13-hzoli13
- X-seq: zsh-workers 979
- From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
- To: kanaya@xxxxxxxxxxxxxxxxxxxxxxxxxxx (Yoshinari KANAYA/金谷吉成)
- Subject: Re: PROMPT_SUBST bug?? zsh-2.6-beta13-hzoli13
- Date: Fri, 3 May 1996 17:25:41 +0200 (MET DST)
- In-reply-to: <14612.831130384@xxxxxxxxxxxxxxxxxxxxxxxxxxx> from Yoshinari KANAYA/=?ISO-2022-JP?B?GyRCNmJDKzVIQC4bKEI=?= at "May 3, 96 10:32:49 pm"
- Organization: Dept. of Comp. Sci., Eotvos University, Budapest, Hungary
- Phone: (36 1)2669833 ext: 2667, home phone: (36 1) 2752368
- Sender: hzoli@xxxxxxxxxx
> Hello zsh experts,
>
> Setting both "setopt correct" and "setopt promptsubst" with
> zsh-2.6-beta13-hzoli13 causes strange behavior.
>
> hostname% setopt correct
>
> hostname% setopt promptsubst
> hostname% exot
> zsh: unmatched '
> zsh: parse error in command substitution
> zsh: correct
> ^(cursor is here)
>
> hostname% unsetopt promptsubst
> hostname% exot
> zsh: correct `exot' to `exit' [nyae]?
>
> Even if there are no startup/shutdown files, this also occurs.
> It was OK with zsh-2.6-beta9. Any suggestions will be greatly
> appreciated.
This is already fixed in beta15-hzoli14 and it will be fixed in beta17.
beta9 also has bugs here which sometimes causes SEGV in spelling
correction.
Zoltan
Messages sorted by:
Reverse Date,
Date,
Thread,
Author