public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "P.J. Kersten" <P.J.Kersten@dia.eur.nl>
To: "Bruce N. Hunsaker" <bruceh@ns1.ieighty.net>
Cc: gnu-win32@cygnus.com
Subject: Re: Bash 2.01 bug in coolview
Date: Sat, 24 Jan 1998 15:34:00 -0000	[thread overview]
Message-ID: <34C858FE.9C0C5172@dia.eur.nl> (raw)
In-Reply-To: <199801201934.MAA09572@ns1.ieighty.net>

Bruce N. Hunsaker wrote:
> 
> In the version of bash.exe that is distributed with coolview
> I have experienced the following problem:
> 
>         $ ls -l | cat
>         $
> No output when using pipes!  In this example, the size of the
> directory makes a difference.  For small directories, it works
> correctly.  Make it a little larger and the output gets truncated.
> Bigger still, and no output will be shown.
> 
> I get better results if I do
>         $ set +o monitor
> but this has no effect if put in .bashrc
> 
> I also get proper results by adding parenthesis:
>         $ (ls -l | cat)
> 
> I have none of these problems with the bash that ships with b18.
> 
> Perhaps there is some other setting for bash I can put
> in .bashrc to fix this problem?

There has been a reported problem with the HUP signal.
Try 
	trap '' 5
in your .bashrc. It works for me.

-- 
Pieter J. Kersten
Erasmus Universiteit Rotterdam
dir. I&A/I&S, WH2-10
Postbus 1738
3000 DR  Rotterdam
Nederland
Tel +31-10-4082599
Fax +31-10-4527236
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  parent reply	other threads:[~1998-01-24 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-20 15:29 Bruce N. Hunsaker
1998-01-24 15:34 ` Jason Tishler
1998-01-24 15:34 ` Kees van Veen
1998-01-24 15:34 ` P.J. Kersten [this message]
1998-01-24 15:34 Chuck Bogorad

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=34C858FE.9C0C5172@dia.eur.nl \
    --to=p.j.kersten@dia.eur.nl \
    --cc=bruceh@ns1.ieighty.net \
    --cc=gnu-win32@cygnus.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).