Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: FreeBSD 5.0 and zsh 3.0.7 rare bug
- X-seq: zsh-workers 12130
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Jeroen Ruigrok/Asmodai <asmodai@xxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: FreeBSD 5.0 and zsh 3.0.7 rare bug
- Date: Sat, 1 Jul 2000 22:37:50 +0000
- Cc: will@xxxxxxxxxxx
- In-reply-to: <20000701225612.J26119@xxxxxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <20000701230320.K26119@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <20000701225612.J26119@xxxxxxxxxxxxxxxxxxxxxxx> <20000701230320.K26119@xxxxxxxxxxxxxxxxxxxxxxx>
(Discussion redirected to zsh-workers.)
On Jul 1, 10:56pm, Jeroen Ruigrok/Asmodai wrote:
} Subject: FreeBSD 5.0 and zsh 3.0.7 rare bug
}
} For some weird reason every now and then my output got arsed.
Arsed?
} After some inspection I came to the discovery that zsh sometimes out of
} itself sets stty's icrnl option. Which obviously messes up output. I
} have no idea what can cause this.
The setting of icrnl shouldn't have any effect on output; the `i' is for
*input*, that is, translate input carriage returns to newlines.
Zsh plays some games with icrnl and inlcr so that type-ahead is handled
properly with respect to the key-bindings for ctrl-M and ctrl-J. There
is a lengthy comment in zle_main.c to explain about this in detail.
On Jul 1, 11:03pm, Jeroen Ruigrok/Asmodai wrote:
} Subject: Re: FreeBSD 5.0 and zsh 3.0.7 rare bug
}
} Something I missed:
}
} stty:
}
} -icrnl
}
} AND
}
} -onlcr
That's not zsh's fault; the only thing zsh does with onlcr is to force
it to be *on*, unless the FreeBSD porters have changed something in
zle_main.c:zsetterm().
--
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