Re: Use of zerr() vs. zwarn()

["Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>]

Welcome back, Sven!  Hope you had a good holiday.

On Oct 4, 11:30am, Sven Wischnowsky wrote:
}
} Bart Schaefer wrote:
} 
} > On Sep 29,  4:58pm, Bart Schaefer wrote:
} > }
} > } 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
} 
} Yes, please. I changed that in 10131.

...??  Not Src/init.c, you didn't.

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

Yes, exactly; that's the same sort of thing I was trying to address with
the other zerr --> zwarn changes.

However, "... only in functions called from completion ..." is not an
error that can possibly occur in any case where a loop *ought* to
continue, is it?

I certainly would *not* advocate changing back anything *else* in 10131.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net