Re: Dired 7.5 bug: Grepping gzipped files problem
Adrian Phillips (adrian.phillips@dnmi.no)
Fri, 30 Sep 94 08:16:59 +0100
>>>>> "sandy" == sandy <sandy@ibm550.sissa.it> writes:
>>>>> On Thu, 29 Sep 94 11:39:58 +0100,
sandy> adrian.phillips@dnmi.no (Adrian Phillips (Tandem
sandy> User)) said:
>> -rw-r--r-- 1 tandem user 59704 Sep 19 14:21 0919.gz -rw-r--r--
>> 1 tandem user 29650 Sep 20 14:17 0920.gz -rw-r--r-- 1 tandem
>> user 20851 Sep 21 15:11 0921.gz
>> the following messages appear: Hits for grep "qemm" in
>> /usr/people/tandem/News/groups/comp.sys.ibm.pc.hardware.misc/0919.gz:
>> zcat: stdin: not in gzip format
sandy> Looks to me like its a problem with either your .gz files
sandy> or zcat. Does it work to zcat them from the shell?
sandy> dired-grep works on gzipped files by zcat'ing them to grep.
sandy> --sandy
I did what I should have done in the first place. I have jka-compr
loaded which means that in the code (I think) :
(setq temp-file
(condition-case err
(file-local-copy file)
(error (progn (setq failed (format "%s" err)) nil))))
when a local copy is made the file is gunzipped while making the local
copy which means when the zcat command is run it doesn't work. Sorry I
don't know what to do about this :-(. Its dired trying to be helpful
with compressed files thats cuasing the problem. Presumably the same
could occur using crypt++ as well.
Adrian
--
-------------------------------------------------------------------------
= Adrian Phillips at | BUT any thoughts in this are purely =
= The Norwegian Meteorological | my own and have nothing to do with =
= Institute | this establishment, thankfully. =
= Net: adrian.phillips@dnmi.no | Phone: 47 22 96 32 09 Fax: 47 22 96 30 50