zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Use of zerr() vs. zwarn()
Date: Wed, 4 Oct 2000 11:30:28 +0200 (MET DST)	[thread overview]
Message-ID: <200010040930.LAA09399@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sat, 30 Sep 2000 16:42:38 +0000


Bart Schaefer wrote:

> On Sep 29,  4:58pm, Bart Schaefer wrote:
> } Subject: Use of zerr() vs. zwarn()
> }
> } init.c:1122:    zwarnnam(name, "option valid only in functions called from completion",
> }   Should these use zerrnam(), as do completion-only conditions within
> }   [[ ... ]] ?
> 
> Judging from the indentation on the line following the call to zwarnnam(),
> I suspect that this originally *was* a call to zerrnam() and was changed
> to zwarnnam() at some point in the past, but I can't find a zsh-workers
> article in the archive to confirm.  (Maybe it was in a uuencoded patch;
> it predates my first local import of 3.1.x, which I believe was 3.1.4.)
> 
> This makes me inclined to leave this whole sub-category alone, at least
> until there's been some feedback.

Yes, please. I changed that in 10131. The discussion leading up to it
is in 10120, 10122 and before. We had problems with builtins stopping
loops (or not) because of errflag.

No opinion or comments on the other things yet...


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-10-04  9:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-04  9:30 Sven Wischnowsky [this message]
2000-10-04  9:47 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-10-04 11:53 Sven Wischnowsky
2000-09-27 19:46 two append bugs? Clint Adams
2000-09-28  3:35 ` Bart Schaefer
2000-09-29 16:58   ` Use of zerr() vs. zwarn() Bart Schaefer
2000-09-30 16:42     ` Bart Schaefer
2000-10-02  0:18     ` Clint Adams

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=200010040930.LAA09399@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).