home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Where do things go when you move them to a folder?
- Message-ID: <1992Dec22.172127.29669@njitgw.njit.edu>
- Date: 22 Dec 92 17:21:27 GMT
- References: <1992Dec18.045538.15204@midway.uchicago.edu> <1992Dec18.113448.774@netcom.com> <1992Dec18.162007.2585@midway.uchicago.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 26
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Dec18.162007.2585@midway.uchicago.edu> pynq@midway.uchicago.edu writes:
- >When I create a folder in \TMP, and move FOO.ZIP to the folder, FOO.ZIP does
- >show up in the directory \tmp\"folder name" (seen from an OS/2 window).
- >However, the drag-n-drop no longer works. It is as if UNZIP (the OS/2
- >32 bit version, from Hobbes) can't unpack files into folders.
- >(Or, at least, folders with funny names...)
-
- Ignore my previous post (I'm going to try and cancel it before it gets
- out of here...).
-
- If your folder or filename has a space in it, UNZIP will choke. It is
- parsing on spaces, and seems to ignore double-quotes. So if you type:
-
- UNZIP "folder/file name"
-
- It will try and unzip "folder/file" and "name". Neither of which
- exists. I know of no solution other than to avoid spaces in the name.
- I think this is a bug in GCC's command-line parsing algorithm. Since
- IBM utilities work fine, I suspect that UnZip will work fine if
- someone recompiles it with C Set/2.
-
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-