public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Editing zipped files with VIM under cygwin
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <20011112155341.L2618@cygbert.vinschen.de> (raw)
Message-ID: <20011111082600.TW38Cxo7fZxUKMoEPsdEEwNL2FfVgC-rV_3XNZmZ0DE@z> (raw)
In-Reply-To: <5A95B0B37820D511AD1500B0D0AADF774DDE44@lbsvnt4>; from BStrohhaecker@Hueller-Hille.com on Mon, Nov 12, 2001 at 02:55:33PM +0100

On Mon, Nov 12, 2001 at 02:55:33PM +0100, Strohhaecker, Bernd wrote:
> BTW, I don't have these problems with vim/gvim compiled with MS VC++ 6.0
> 
> editing *.gz-files works, but in 1st call there's an error message:
> 
> ...
> Ausführung von BufRead Auto-Kommandos für "*.gz"
> Autokommando call s:read("gzip -d")
> Rufe Shell auf, um "(which gzip) >/tmp/v568240/0 2>&1" auszuführen
> 
> Fehler beim Ausführen von "function <SNR>11_read..<SNR>11_check":
> Zeile    3:
> Datei "/tmp/v568240/0" kann nicht gelesen werden
> Rufe Shell auf, um "(gzip --version) >/tmp/v568240/1 2>&1" auszuführen
>                            d /tmp/v568240/2.gz) >/tmp/v568240/3 2>&1"
> auszuführe
> n
> Ausführung von BufEnter Auto-Kommandos für "*"
> ...
> 
> Editing *.bz2-files does not work, the 1st call shows:
> 
> ...
> Ausführung von BufRead Auto-Kommandos für "*.bz2"
> Autokommando call s:read("bzip2 -d")
> Rufe Shell auf, um "(which bzip2) >/tmp/v568240/6 2>&1" auszuführen
> 
> Fehler beim Ausführen von "function <SNR>11_read..<SNR>11_check":
> Zeile    3:
> Datei "/tmp/v568240/6" kann nicht gelesen werden
> Rufe Shell auf, um "(bzip2 --version) >/tmp/v568240/7 2>&1" auszuführen
> 
> Zeile    5:
> Datei "/tmp/v568240/7" kann nicht gelesen werden
> ...
> 
> "bzip2 --version >x 2>&1" seems to wait for an input/EOF ???

Dunno.  I've just checked it here in tty and notty mode and
I don't have that problem.  Reading both, gzipped and bzipped
files wors fine.  Are you using *gasp* cmd as shell?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

  reply	other threads:[~2001-11-12 14:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 10:24 Strohhaecker, Bernd
2001-11-01 10:35 ` Corinna Vinschen [this message]
2001-11-11  8:26   ` Corinna Vinschen
2001-11-11  8:26 ` Strohhaecker, Bernd
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 23:45 Strohhaecker, Bernd
2001-11-02  0:58 ` Corinna Vinschen
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-11  8:26 Strohhaecker, Bernd
2001-11-11  8:26 Strohhaecker, Bernd
2001-11-11  8:26 ` Corinna Vinschen

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=20011112155341.L2618@cygbert.vinschen.de \
    --to=cygwin@cygwin.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).