Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh weird behaviour (possibly bug?)
- X-seq: zsh-workers 23642
- From: Peter Stephenson <pws@xxxxxxx>
- Subject: Re: zsh weird behaviour (possibly bug?)
- Date: Mon, 02 Jul 2007 17:50:17 +0100
- Cc: "Janos Barbero" <jbarbero@xxxxxxxxx>, zsh-workers@xxxxxxxxxx (Zsh hackers list)
- In-reply-to: <200707021640.l62GeJfj010435@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <77d935a0707012032u6011f3d1scf97e399ef7c5fa3@xxxxxxxxxxxxxx> <200707020929.l629Tgfw003908@xxxxxxxxxxxxxx> <77d935a0707020917o244fc086k72a679839d4f256b@xxxxxxxxxxxxxx> <200707021640.l62GeJfj010435@xxxxxxxxxxxxxx>
Peter Stephenson wrote:
> In that case it might be worth trying to run screen or zsh under strace and
> seeing if anything funny is happening with I/O. You'll get lots of
> useless output, but (if the strings are recognizable enough) it should
> be possible to work out what's going where.
Come to think of it, it's not clear that looking at I/O from the shell
is going to tell you much: opens and ioctls might, but the command
that's not showing output,
ls | sed 's/\<\(.\)\([^ ]*\)/\u\1\L\2/g'
doesn't have output going through the shell. The shell forks, set's up
the pipe, and forks again; one of the forked shells execs ls, the other
sed. The output goes straight from ls to sed to the terminal.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview
Messages sorted by:
Reverse Date,
Date,
Thread,
Author