unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Compressing the Lisp and Info files in the MS-Windows installation
Date: Tue, 16 Apr 2013 11:55:57 +0300	[thread overview]
Message-ID: <83zjwy4zxe.fsf@gnu.org> (raw)
In-Reply-To: <4ACDB1853730452BA136101AAAA5B3D1@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <emacs-devel@gnu.org>
> Date: Mon, 15 Apr 2013 13:13:14 -0700
> 
> And even if they have gzip, some users will likely want to unzip all of the .el
> so that they can more easily grep etc.

How is this different from users on Posix platforms?

In any case, uncompressing all of the files is easy on any platform
that has gzip installed.

> Is the gain from compression worth making them go through that extra
> step?

I don't know the answer to that.  I asked this question (and stated
the disk space savings) to hear opinions.  Hearing questions instead
of answers doesn't really help ;-)

> Even though Emacs is bigger now than in the past, I would think that size
> (download & disk) is generally less of a problem nowadays than it used to be.

Indeed.  But still on Posix platforms, compression is the default for
some reasons, although these same considerations clearly apply there
as well.



  reply	other threads:[~2013-04-16  8:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 15:26 Compressing the Lisp and Info files in the MS-Windows installation Eli Zaretskii
2013-04-15 20:02 ` Stefan Monnier
2013-04-15 20:13   ` Drew Adams
2013-04-16  8:55     ` Eli Zaretskii [this message]
2013-04-16 13:23       ` Drew Adams
2013-05-08 13:02       ` Steinar Bang
2013-04-16  8:50   ` Eli Zaretskii
2013-04-16 13:10     ` Stefan Monnier
2013-04-16 14:33       ` Eli Zaretskii
2013-04-16  8:18 ` Stephen J. Turnbull
2013-04-16  9:10   ` Eli Zaretskii

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=83zjwy4zxe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).