zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>, zsh-workers@math.gatech.edu
Subject: Re: Correction Bug in Beta 17
Date: Wed, 8 May 1996 18:30:25 -0700	[thread overview]
Message-ID: <960508183026.ZM23468@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: Correction Bug in Beta 17" (May  9, 12:28am)

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



  reply	other threads:[~1996-05-09  1:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-08 17:10 Eskandar Ensafi
1996-05-08 17:33 ` Mark Borges
1996-05-08 22:28 ` Zoltan Hidvegi
1996-05-09  1:30   ` Bart Schaefer [this message]
1996-05-09  7:34   ` Peter Stephenson
1996-05-10 11:01     ` Zoltan Hidvegi
     [not found] <mdb@cdc.noaa.GOV>
1996-05-08 20:01 ` Danek Duvall

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=960508183026.ZM23468@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --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).