From: Andrey Borzenkov <arvidjaar@newmail.ru>
To: zsh-workers@sunsite.dk
Cc: "Larry P. Schrof" <larry@schrof.net>
Subject: Re: (Revisited): zsh + less == hard hang of tty.
Date: Tue, 26 Sep 2006 22:15:24 +0400 [thread overview]
Message-ID: <200609262215.24576.arvidjaar@newmail.ru> (raw)
In-Reply-To: <200609261750.k8QHoAXv002753@news01.csr.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 26 September 2006 21:50, Peter Stephenson wrote:
> "Larry P. Schrof" wrote:
> > - When I get a Linux tty to hang by doing this, log in on another tty,
> > and kill the *less* process, it terminates, and any I/O that was in
> > the buffer (from my extra keystrokes while less was hung) get
> > interpreted by the shell. zsh becomes responsive again.
>
> Sounds from this you may need to run strace on the less inside
> the zsh -c (or just do it interactively), since zsh appears to be
> just blithely waiting. We'll probably find less is trying to
> grab the terminal and failing, or something like that... quite
> what we do if that's the case, I'm not sure.
I have been running the same versions for quite some time without any problem
(nor do I now have problem with zsh CVS). One thing to check is what
LESSPIPE (or other LESSxxxx) environments set to and try with all of them
unset first.
The only other thing that comes in mind is some weird interaction with job
control.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFGW48R6LMutpd94wRAoVkAJ9lxLqhk565YT2ttHqdBwjt0OtlQACgnJdx
Zn4+97A0rtI16apU0XSkQak=
=RUyL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-09-26 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060926142946.GA1608@lucien.blight.com>
2006-09-26 17:00 ` Peter Stephenson
2006-09-26 17:26 ` Larry P. Schrof
2006-09-26 17:50 ` Peter Stephenson
2006-09-26 18:15 ` Andrey Borzenkov [this message]
2006-09-26 19:05 ` Larry P. Schrof
2006-09-27 2:43 ` Andrey Borzenkov
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=200609262215.24576.arvidjaar@newmail.ru \
--to=arvidjaar@newmail.ru \
--cc=larry@schrof.net \
--cc=zsh-workers@sunsite.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).