From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, zsh-workers@sunsite.auc.dk
Cc: will@FreeBSD.org
Subject: Re: FreeBSD 5.0 and zsh 3.0.7 rare bug
Date: Sat, 1 Jul 2000 22:37:50 +0000 [thread overview]
Message-ID: <1000701223750.ZM9579@candle.brasslantern.com> (raw)
In-Reply-To: <20000701225612.J26119@daemon.ninth-circle.org>
In-Reply-To: <20000701230320.K26119@daemon.ninth-circle.org>
(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
parent reply other threads:[~2000-07-01 22:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20000701230320.K26119@daemon.ninth-circle.org>]
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=1000701223750.ZM9579@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=asmodai@wxs.nl \
--cc=will@FreeBSD.org \
--cc=zsh-workers@sunsite.auc.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).