From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Helmut Jarausch" <jarausch@numa1.igpm.rwth-aachen.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: Debug / cut'n'paste on IRIX
Date: Fri, 12 Mar 1999 13:21:30 +0300 [thread overview]
Message-ID: <001201be6c72$18aaa260$21c9ca95@mowp.siemens.ru> (raw)
[I am sorry for all these mails]
>
> that's what happens. I could not find the relevant part in
> sources - anybody (Geoff) - could you get a look:
>
> Cut'n'pasted in another shell. As you see, after it gets first
> new line it does ioctl(10, TCSETSW,...) before PS2, that,
> unfortunately, throughs away all pending input :-( The following
> FIONREAD is useless in this case.
>
Looks, like it is done in settyinfo(), that is (unconditionally) called from
trashzle() that is called from zleread() after we've seen new line. (It is
actually using tcsetattr() on our system)
Fixing it is probably not trivial. Currently, the only place where FIONREAD
is used is setupterm(). If we find typeahed, we avoid calling sttyinfo() at
all. May be, we should come up with a single function that checks for
typeahead, reads it in buffer and changes tty modes after that?
And I wonder, if this is all ... We already had (still unresolved) case with
read -q ...
/andrej
next reply other threads:[~1999-03-12 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 10:21 Andrej Borsenkow [this message]
1999-03-12 10:34 ` Peter Stephenson
1999-03-12 14:02 ` PATCH: " Peter Stephenson
1999-03-15 8:19 ` Andrej Borsenkow
1999-03-15 9:38 ` PATCH: 3.1.5-pws-12: configuration changes Peter Stephenson
1999-03-12 14:33 ` Debug / cut'n'paste on IRIX Geoff Wing
1999-03-15 9:31 ` up-line-or-history and multiline input (was: RE: Debug / cut'n'paste on IRIX) Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
1999-03-12 9:40 Debug / cut'n'paste on IRIX Andrej Borsenkow
1999-03-12 9:04 Helmut Jarausch
1999-03-12 9:20 ` Andrej Borsenkow
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='001201be6c72$18aaa260$21c9ca95@mowp.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=jarausch@numa1.igpm.rwth-aachen.de \
--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).