unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10990@debbugs.gnu.org
Subject: bug#10990: 24.0.94; Uncompressing files
Date: Mon, 12 Mar 2012 05:52:15 +0200	[thread overview]
Message-ID: <83boo2xyq8.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0gStaC6Ax-MDENU14RTjxo+b7RSJ6dB3=8HBaHyMv0isw@mail.gmail.com>

> Date: Sun, 11 Mar 2012 22:50:06 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 10990@debbugs.gnu.org
> 
> Well, it's obvious that there is no "gunzip" executable visible from
> my environment.  I knew that.  And it is also obvious that I don't
> need it.  The problem is not that my system is lacking an
> uncompression program (I have "gzip -d"), the problem is that Emacs
> (a) doesn't know how to invoke it, and (b) doesn't let me tell it how.

gzip and gunzip are parts of the same package.  It is reasonable to
assume that having one means you also have the other.

But it sounds like you don't actually want to solve your problem, but
rather make some point about big bad Emacs.  Whatever.

> > Visiting compressed files uses "gzip -d", so it doesn't need gunzip.
> > See lisp/jka-cmpr-hook.el.
> 
> Then, why doesn't Emacs use that same method whenever it needs to
> uncompress a file?

Because dired uses a different code which was written by a different
person, I guess.  That code needs a program name, not a shell command,
so "gzip -d" will not do.

> If Emacs was consistent in this regard and used "gzip -d" whenever it
> need to uncompress a file, I would not have had any problem.

I don't see why there should be a consistency in this case.

> > I submit that your system is misconfigured
> 
> ???
> I showed clearly that my system is capable of uncompressing files
> compressed by Emacs.

You have only half of a package installed.





  reply	other threads:[~2012-03-12  3:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11  8:23 bug#10990: 24.0.94; Uncompressing files Dani Moncayo
2012-03-11 16:48 ` Eli Zaretskii
2012-03-11 21:50   ` Dani Moncayo
2012-03-12  3:52     ` Eli Zaretskii [this message]
2012-03-12  7:46       ` Dani Moncayo
2012-03-12 17:28         ` Juanma Barranquero
2012-03-12 17:29         ` Eli Zaretskii
2012-03-12 19:12           ` Dani Moncayo
2012-03-12 20:12             ` Stefan Monnier
2012-03-12 20:58             ` Eli Zaretskii
2012-03-12 17:58         ` Achim Gratz
2012-03-12 20:47           ` Achim Gratz
2012-03-12 20:59           ` Eli Zaretskii
2012-03-12 21:50             ` Achim Gratz
2021-08-31 16:20 ` Marco Centurion
2021-09-01  7:37   ` Lars Ingebrigtsen

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=83boo2xyq8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=10990@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    /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).