-*- text -*-
------------------------------------------------------------------------
% ( echo foo ; echo bar 1>& 2 ) 2>&1 1>/dev/null | cat
bar
foo
% ksh
$ ( echo foo ; echo bar 1>& 2 ) 2>&1 1>/dev/null | cat
bar

This is not exactly a bug, but an effect of the multiple IO
redirection.  It is a (k)sh incompatibility, though.
------------------------------------------------------------------------
Completion has a habit of doing the wrong thing after a
backslash/newline.
------------------------------------------------------------------------
If you suspend "man", zle seems to get into cooked mode.  It works ok
for plain "less".
------------------------------------------------------------------------
Redisplay zle function does not work.
------------------------------------------------------------------------
single_line_zle does not go to the next line after return.
------------------------------------------------------------------------
% test=test
% echo "${test##`echo '*'`}"
test
sh gives empty string here. Is it a bug or a feature?
------------------------------------------------------------------------
% zsh -c 'cat a_long_file | less'
can be interrupted with ^C. The prompt comes back and less is orphaed.
If you go to the end of the file with less and cat terminates, ^C
will not terminate less.
------------------------------------------------------------------------
On Suns in xterm if a line wraps to the next line and the cursor is in
the last column on the sreen and you type a character the charactr after
the cursor is replaced on the screen with the character the cursor is on.
------------------------------------------------------------------------
Only waste is stored in the variable given to read -k if there is a
character immediately avaible for reading. In this case that character
is not even removed from the input buffer. Try
% sleep 1 ; read -k ch
and press a key while it's sleeping then examine $ch.
------------------------------------------------------------------------
The pattern %?* maches names beginning with %? instead of names with at
least two characters beginning with %. This is a hack to allow %?foo job
substitution without quoting. This behaviour is incompatible with sh
and ksh and may be removed in the future. A good fix would be to keep
such patterns unchanged if they do not match regardless of the state of
the nonomatch and nullglob options.
------------------------------------------------------------------------

