From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: older issues
Date: Thu, 21 Feb 2002 07:09:33 +0000 [thread overview]
Message-ID: <1020221070933.ZM1882@candle.brasslantern.com> (raw)
In-Reply-To: <20020221041555.GA6556@dman.com>
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
next prev parent reply other threads:[~2002-02-21 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 4:15 Clint Adams
2002-02-21 7:09 ` Bart Schaefer [this message]
2002-02-21 13:21 ` PATCH: RANDOM docs Clint Adams
2002-02-21 13:39 ` older issues Clint Adams
2002-02-21 15:09 ` Etc/.distfiles Bart Schaefer
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=1020221070933.ZM1882@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).