5 On some terminals, display of lines with exactly 80 characters is
6 problematic. zsh assumes that the terminal does not print an extra
7 newline in this case, but some terminals (e.g. aixterm) do.
8 ------------------------------------------------------------------------
9 When interrupting code like the following with ^C:
13 if the `sh' is executing, zsh does not know that the sh received a ^C and
14 continues with the next iteration. This happens for any program which
15 handles the interrupt, then exits after tidying up; it does not happen for
16 zsh, which exits directly from the signal handler. The workaround is to
17 use ^Z which forks the shell and makes the loop a separate job, then kill
19 ------------------------------------------------------------------------
20 If you suspend "man", zle seems to get into cooked mode. It works ok
22 It is not specific neither to man nor to zsh.
23 E.g. call the following program foo:
27 int main(int argc, char *argv[])
31 if (!fork()) /* child */
32 execvp(argv[1], argv + 1);
38 from zsh/bash, zle/readline gets into cooked mode.
39 ------------------------------------------------------------------------
40 The pattern %?* matches names beginning with %? instead of names with at
41 least two characters beginning with %. This is a hack to allow %?foo job
42 substitution without quoting. This behaviour is incompatible with sh
43 and ksh and may be removed in the future. A good fix would be to keep
44 such patterns unchanged if they do not match regardless of the state of
45 the nonomatch and nullglob options.
46 ------------------------------------------------------------------------
47 It is currently impossible to time builtins.
48 ------------------------------------------------------------------------