Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: older issues
- X-seq: zsh-workers 16684
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: older issues
- Date: Thu, 21 Feb 2002 07:09:33 +0000
- In-reply-to: <20020221041555.GA6556@xxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020221041555.GA6556@xxxxxxxx>
On Feb 20, 11:15pm, Clint Adams wrote:
} Subject: older issues
}
} I think that each of the following should either be put into Etc/BUGS or
} the documentation. Any comments?
}
} * Unrandom $RANDOM in subshells
Not a bug, so definitely shouldn't be in BUGS. The doc for RANDOM could
make it more explicit that the results are is an intentionally repeatable
psuedo-random sequence.
} * time and repeat builtins don't mix
What does this mean? "repeat N time ..." works fine; "time repeat N ..."
works just as well as "time" works with any other builtin (which is to
say, it doesn't time builtins at all). There's no reason to record this
_specific_ instance of "time" not working with a builtin.
} * certain prompt expansions are elided if LINES<3
As I just noted in another message, this is a SINGLE_LINE_ZLE effect, and
is not a bug per se.
} * Zsh should clean up its signals on startup
I think zsh already does exactly the "cleaning up" that it means to. I
don't agree with what you think it "should" do.
I'm not sure where to document the behavior; Invocation? Jobs & Signals?
(The "Signals" subsection is pretty brief.)
} * zsh does not know how to handle multibyte characters
That belongs on a TODO list, not in a BUGS file or the doc.
--
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author