From: "Xah Lee" <xah@xahlee.org>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 4867@emacsbugs.donarmstrong.com
Subject: bug#4867: 23.1; dired cannot find gunzip with Z; Windows
Date: Thu, 5 Nov 2009 13:12:30 -0800 [thread overview]
Message-ID: <664A39468EC9464BAE3CFF2D86FD5E56@xahPC> (raw)
In-Reply-To: <83bpjgbtbq.fsf@gnu.org>
> It's better to change the last line to
>
> gzip -d %*
>
> because then you will be able to give more than one argument to this
> batch file. E.g., if you want to pass additional switches or unpack
> several files.
Thanks for the tip. I followed your advice on my machine.
> Anyway, why do you have gunzip as a shell script? I looked at a
> native Windows port and on a GNU/Linux box, and they both have gunzip
> as a first-class binary executable program.
Cygwin and msys both use a shell script for some reason.
Xah
----- Original Message -----
From: "Eli Zaretskii" <eliz@gnu.org>
To: "Xah Lee" <xah@xahlee.org>
Cc: <4867@emacsbugs.donarmstrong.com>
Sent: Thursday, November 05, 2009 12:38 PM
Subject: Re: bug#4867: 23.1; dired cannot find gunzip with Z; Windows
>> From: "Xah Lee" <xah@xahlee.org>
>> Date: Thu, 5 Nov 2009 12:25:14 -0800
>>
>> Found a solution. Create a file name gunzip.bat, with this content:
>>
>> @echo off
>> gzip -d %1
>
> It's better to change the last line to
>
> gzip -d %*
>
> because then you will be able to give more than one argument to this
> batch file. E.g., if you want to pass additional switches or unpack
> several files.
>
>> I think this should still considered a bug though. Considering it as a
>> Windows OS problem isn't very helpful in solving this. I'm sure if
>> similar
>> problems happen in linux that's OS issue, people probably will not look
>> at
>> it as “Oh, it's OS issue, emacs doesn't need to deal with it”.
>
> If you try the same with a Windows batch file on GNU/Linux, Emacs will
> barf there as well. Emacs behave according to the rules of the host
> OS, so you cannot expect it to be able to run alien executables from
> some other OS that the host does not recognize as executables and
> doesn't know how to run.
>
> Anyway, why do you have gunzip as a shell script? I looked at a
> native Windows port and on a GNU/Linux box, and they both have gunzip
> as a first-class binary executable program.
prev parent reply other threads:[~2009-11-05 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83iqdoby3a.fsf@gnu.org>
2009-11-04 16:56 ` bug#4867: 23.1; dired cannot find gunzip with Z; Windows Xah Lee
2009-11-05 19:05 ` bug#4867: marked as done (23.1; dired cannot find gunzip with Z; Windows) Emacs bug Tracking System
[not found] ` <7DD094C4BE9F42B7965A217C4B33E7FF@xahPC>
2009-11-05 20:38 ` bug#4867: 23.1; dired cannot find gunzip with Z; Windows Eli Zaretskii
2009-11-05 21:12 ` Xah Lee [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=664A39468EC9464BAE3CFF2D86FD5E56@xahPC \
--to=xah@xahlee.org \
--cc=4867@emacsbugs.donarmstrong.com \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).