From: Will Parsons <varro@nodomain.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: file uncompression with native Windows Emacs
Date: Fri, 9 Dec 2016 21:33:00 -0500 [thread overview]
Message-ID: <slrno4mqat.1eap.varro@anukis.local> (raw)
In-Reply-To: o2ehmi013u1@news6.newsguy.com
On Friday, 9 Dec 2016 10:10 AM -0500, B. T. Raven wrote:
> On 12/8/2016 19:29, Will Parsons wrote:
>> I'm confused about what I should expect for file uncompression with
>> native Windows Emacs. I'm running:
>>
>> GNU Emacs 25.1.1 (i686-w64-mingw32)
>>
>> Curiously, if I visit a file compressed with bzip2, Emacs has no
>> problem opening it, but if I visit a file compressed with gzip, Emacs
>> complains that "Uncompression program 'gzip' not found".
>>
>> How is this supposed to work? I don't see any compression binaries
>> packages in the Emacs installation directory, but I do have an
>> ezwinports directory that contains bzip2 utilities, so perhaps Emacs
>> is using that (but how does it know?) If ezwinports is the source of
>> bzip2 for Emacs, I don't see similar gzip utilities, so I'm quite
>> confused.
>
> ezwinports is probably in your path. Type "where bzip2.exe" to see if
> this is so. A couple of gzip binaries for w32 are here:
You're absolutely right.
> http://www.gzip.org/ ;; put them one of them in the same directory
> where bzip2 is now and emacs should find it.
I downloaded a Windows version of the gzip utilities from gnuwin32 and
put them in a directory in my PATH, and now Emacs has no difficulty
opening them. I had expected a more "official" way of handling
(de)compression, but I'm happy. Thanks!
--
Will
next prev parent reply other threads:[~2016-12-10 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 1:29 file uncompression with native Windows Emacs Will Parsons
2016-12-09 8:16 ` Eli Zaretskii
2016-12-09 15:16 ` Óscar Fuentes
2016-12-09 15:10 ` B. T. Raven
2016-12-10 2:33 ` Will Parsons [this message]
2016-12-13 23:13 ` Gene
2016-12-14 6:26 ` Jonathan Groll
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=slrno4mqat.1eap.varro@anukis.local \
--to=varro@nodomain.invalid \
--cc=gyliamos@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.