gvim64/win7 claims error on unzip, but unzip get no error, why?
Linda W
I tried to open a .jar file in gvim (7.3). and got an error (which one
has to type in manually, as vim won't let you cut/paste -- a much
maligned user-hindrance, when it was first widely used by Microsoft):
unzip: cannot find or open C:/Users/lindaw/AppData/Roaming/....
So I open up a console window and try the command:
(and)...
***warning*** (zip#Browse) ... same message as above....
/Users/lindaw> unzip -l
C:/users/lindaw/AppData/Roaming/Mozilla/Firefox/Profiles/lindaw/extensions/{funnynumber}/chrome/file.jar
Archive:
C:/users/lindaw/AppData/Roaming/Mozilla/Firefox/Profiles/lindaw/extensions/{funnynumber}/chrome/file.jar
Length Date Time Name
--------- ---------- ----- ----
1109 09-29-2011 07:39 content/menucommander.js
14574 09-29-2011 07:39 content/browser.js
22524 09-29-2011 07:39 content/script.js
3416 09-29-2011 07:39 content/install.js
....
---
I.e. works just fine...
So why didn't it work in Vim? Doesn't make sense.
My first guess is it is I mistakenly installed broken 32-bit version and
it couldn't call the right programs or access the right files due to
windows redirection, but I can't think of any of the programs in this
case, that it would have called where it needed a 64-bit version, so I'm
stumped...
Why does it work at the shell, but not from Vim?
Charles Campbell
* is the path that vim uses for your shell the same as the path your
shell uses? (I'm not at a windows computer; perhaps :!echo %PATH%
* is vim using the shell you expect? :echo &shell
* The message that you're getting, "...cannot find..." is not being
issued directly by zip.vim; does it work if you use backslashes instead
of slashes?
Well, that's a start, anyway.
Regards,
Chip Campbell
Ben Fritz
On Oct 21, 1:02 pm, Linda W <v...@tlinx.org> wrote:
> I tried to open a .jar file in gvim (7.3). and got an error (which one
> has to type in manually, as vim won't let you cut/paste -- a much
> maligned user-hindrance, when it was first widely used by Microsoft):
>
an error from a shell command, in which case it should be in a shell
window, not Vim's fault. Or maybe it's the output of an ex command, in
which case :redir will let you grab the output.
Benjamin R. Haskell
My guess would be that you're attempting to use a Cygwin or MSYS version
of unzip from a Windows-native version of Vim. Or vice versa,
perhaps... Either way you might run into directory separator issues.
What do you get from unzip -v (or --version, maybe)?
How about :version (from within Vim -- just the lines up to the start of
the features)?
Also, are you typing exactly what's on-screen? Or are you using '/' in
place of '\'?
--
Best,
Ben
Linda W
I typed in exactly what I saw on the screen. (I try to use / whenever I
can)....
It used to work in in XP and before, but they disallowed compat in Win7
(dunno about vista).
I searched my machine, there is only 1 unzip on my machine in C:\bin.
(Cygwin).
It works from shell --
They both have C:\bin in the path, first, followed by C:\Prog64\vim.
The path in vim also has a 2nd entry for C:\Prog64\vim.
So the same program is being invoked with what appears to be the same path.
In one case it gives a listing, in the other, 'not found'...
It includes a drive letter in both cases...
Maybe vim appends a CR to the path name or something? I have it set
for unix line endings,
only (LF)?
version in vim = 7.3,, MSWin 32bit gui with ole support
unzip:
nZip 6.00 of 20 April 2009, by Cygwin. Original by Info-ZIP.
Latest sources and executables are at ftp://ftp.info-zip.org/pub/infozip/ ;
see ftp://ftp.info-zip.org/pub/infozip/UnZip.html for other sites.
Compiled with gcc 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) for
Unix (Cygwin) on Aug 4 2009.
UnZip special compilation options:
ASM_CRC
COPYRIGHT_CLEAN (PKZIP 0.9x unreducing method not supported)
SET_DIR_ATTRIB
SYMLINKS (symbolic links supported, if RTL and file system permit)
TIMESTAMP
UNIXBACKUP
USE_EF_UT_TIME
USE_UNSHRINK (PKZIP/Zip 1.x unshrinking method supported)
USE_DEFLATE64 (PKZIP 4.x Deflate64(tm) supported)
UNICODE_SUPPORT [char coding: UTF-8] (handle UTF-8 paths)
MBCS-support (multibyte character support, MB_CUR_MAX = 6)
LARGE_FILE_SUPPORT (large files over 2 GiB supported)
ZIP64_SUPPORT (archives using Zip64 for large files supported)
USE_BZIP2 (PKZIP 4.6+, using bzip2 lib version 1.0.5, 10-Dec-2007)
VMS_TEXT_CONV
WILD_STOP_AT_DIR
[decryption, version 2.11 of 05 Jan 2007]
UnZip and ZipInfo environment options:
UNZIP: [none]
UNZIPOPT: [none]
ZIPINFO: [none]
ZIPINFOOPT: [none]
Still somewhat of a mystery...