From: "Strohhaecker, Bernd" <BStrohhaecker@Hueller-Hille.com>
To: cygwin@sources.redhat.com
Subject: Re: Editing zipped files with VIM under cygwin
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <5A95B0B37820D511AD1500B0D0AADF774DDE4C@lbsvnt4> (raw)
Message-ID: <20011111082600.xsFQJmxf0e0WAbjkPAASj5NNw36DAplgmuirrSRUbAo@z> (raw)
> -----Ursprüngliche Nachricht-----
> Von: Corinna Vinschen [SMTP:cygwin@cygwin.com]
> Gesendet am: Dienstag, 13. November 2001 14:01
> An: cygwin@cygwin.com
> Betreff: Re: Editing zipped files with VIM under cygwin
>
> On Tue, Nov 13, 2001 at 12:03:19PM +0100, Strohhaecker, Bernd wrote:
> > let e = executable(name)
> > This fails on my (cygwin-)system for any program:
> > :echo executable("bash")
> > Rufe Shell auf, um "(which bash) >/tmp/v645258/1 2>&1" auszuführen
> >
> > Datei "/tmp/v645258/1" kann nicht gelesen werden-1
>
> Did you install the which package? `which' is not a bash
> internal command.
Yes, I've installed latest/which/which-1.4.tar.gz
> > 2. 'bzip2 --version > xx' doesn't finish.
>
> I can reproduce that but don't know why that happens, currently.
>
> Corinna
> -----Ursprüngliche Nachricht-----
> Von: Michael Schaap [SMTP:cygwin@mscha.com]
> Gesendet am: Dienstag, 13. November 2001 14:35
> An: cygwin@cygwin.com
> Betreff: Re: Editing zipped files with VIM under cygwin
>
> ...
>
> As you can see, the --version flag doesn't stop bzip2 from trying to
> compress standard input.
> Possible workarounds:
>
> $bzip2 --version --help 2>qqq
>
> $bzip2 --version </dev/null >/dev/null 2>qqq
>
> - Michael
Yes, thanks, taking a look at bzip2.c shows, that there's
simply no exit-call after displaying the license.
Is the following patch reasonable ?
--
Bernd
$ diff -u bzip2.c.org bzip2.c
--- bzip2.c.org Tue Nov 13 14:43:09 2001
+++ bzip2.c Tue Nov 13 14:44:20 2001
@@ -1632,6 +1632,7 @@
" \n",
BZ2_bzlibVersion()
);
+ exit(1);
}
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-11-13 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 23:45 Strohhaecker, Bernd [this message]
2001-11-02 0:58 ` Corinna Vinschen
2001-11-11 8:26 ` Corinna Vinschen
2001-11-11 8:26 ` Strohhaecker, Bernd
-- strict thread matches above, loose matches on Subject: below --
2001-11-11 8:26 Strohhaecker, Bernd
2001-11-11 8:26 ` Corinna Vinschen
2001-11-11 8:26 Strohhaecker, Bernd
2001-11-11 8:26 Strohhaecker, Bernd
2001-11-11 8:26 ` Corinna Vinschen
2001-11-11 8:26 ` Corinna Vinschen
2001-11-01 20:30 Strohhaecker, Bernd
2001-11-01 21:14 ` Corinna Vinschen
2001-11-01 21:24 ` Michael Schaap
2001-11-11 8:26 ` Michael Schaap
2001-11-11 8:26 ` Corinna Vinschen
2001-11-11 8:26 ` Strohhaecker, Bernd
2001-11-01 10:24 Strohhaecker, Bernd
2001-11-01 10:35 ` Corinna Vinschen
2001-11-11 8:26 ` Corinna Vinschen
2001-11-11 8:26 ` Strohhaecker, Bernd
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=5A95B0B37820D511AD1500B0D0AADF774DDE4C@lbsvnt4 \
--to=bstrohhaecker@hueller-hille.com \
--cc=cygwin@sources.redhat.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).