From: "Chuck Bogorad" <chuck@ethereal.ru>
To: "gnu-win32" <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: <01bd27de$ded8e020$0100a8c0@hysteria.spb.ru> (raw)
>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.
Seems to be a problem in coolview. If you do "set | vim -", vim
says: "Vim: Caught deadly signal HUP" - something is sending the
HUP signal. Don't know what.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1998-01-24 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-24 15:34 Chuck Bogorad [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-01-20 15:29 Bruce N. Hunsaker
1998-01-24 15:34 ` P.J. Kersten
1998-01-24 15:34 ` Kees van Veen
1998-01-24 15:34 ` Jason Tishler
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='01bd27de$ded8e020$0100a8c0@hysteria.spb.ru' \
--to=chuck@ethereal.ru \
--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).