Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Correction Bug in Beta 17
- X-seq: zsh-workers 1034
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Zoltan Hidvegi <hzoli@xxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Correction Bug in Beta 17
- Date: Wed, 8 May 1996 18:30:25 -0700
- In-reply-to: Zoltan Hidvegi <hzoli@xxxxxxxxxx> "Re: Correction Bug in Beta 17" (May 9, 12:28am)
- References: <199605082228.AAA00309@xxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On May 9, 12:28am, Zoltan Hidvegi wrote:
} Subject: Re: Correction Bug in Beta 17
}
} > With the PROMPT_SUBST option set in zsh-2.6-beta17, the spelling correction
} > prompt is totally messed up, and two bogus error messages are produced:
} >
} > 1% setopt correct
} > 2% setopt promptsubst
} > 3% ks
} > zsh: unmatched '
} > zsh: parse error in command substitution
} > zsh: correct n
} > zsh: command not found: ks
}
} This is not a bug. And the error messages are correct. SPROMPT is
} initialised to
}
} zsh: correct `%R' to `%r' [nyae]?
}
} If you tund on GLOB_SUBST, zsh will try to expand it so interprets ` as
} command substitution.
Sorry, Zoltan, but I'd say that *IS* a bug. If the initialization of
SPROMPT causes zsh to produce error messages when an option is set,
then I'd say SPROMPT ought not to be initialized to that. The user
shouldn't have to know that he can't set certain combinations of options
without also changing his prompts. That's just too silly.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
Messages sorted by:
Reverse Date,
Date,
Thread,
Author