all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
Cc: Juri Linkov <juri@jurta.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: TUTORIAL.gz
Date: Mon, 17 Oct 2005 17:03:00 +0100	[thread overview]
Message-ID: <4715FA60-84CE-4FCE-9F68-644D8C63AE73@gmail.com> (raw)
In-Reply-To: <jwvzmp8tdgx.fsf-monnier+emacs@gnu.org>

On 17 Oct 2005, at 15:46, Stefan Monnier wrote:
>
> Agreed.  Except that let-binding auto-compression-mode doesn't do much
> if anything.  Better just check whether auto-compression-mode is  
> nil and if
> so don't try to load the .gz file.

Seems like I got confused by instructions from jka-compr.el:

;; To use jka-compr, invoke the command `auto-compression-mode' (which
;; see), or customize the variable of the same name.  Its operation
;; should be transparent to the user (except for messages appearing when
;; a file is being compressed or uncompressed).

The DOC strings are much clearer regarding this issue.

Shouldn't we better enable auto-compression-mode temporarily if it is  
switched off? I mean, if a site-wide installation (or distribution)  
compresses stuff like tutorials and, more importantly, things like  
NEWS, then Emacs should load these files on request no matter whether  
the user has turned off auto-compression-mode. It would be seen as a  
bug if it didn't.


> Actually, jka-compr.el should provide a list of extensions it  
> understands,
> so we wouldn't have to hard-code .gz here.  I guess jka-compr-load- 
> suffixes
> could be used for that.

Isn't it more than enough to support distribution-wide .gz compression?

  reply	other threads:[~2005-10-17 16:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11 23:39 TUTORIAL.gz David Reitter
2005-10-13 20:11 ` TUTORIAL.gz Richard M. Stallman
2005-10-14  9:16   ` TUTORIAL.gz Werner LEMBERG
2005-10-14 10:07     ` TUTORIAL.gz David Kastrup
2005-10-14 10:51       ` TUTORIAL.gz Werner LEMBERG
2005-10-15 16:13         ` TUTORIAL.gz Richard M. Stallman
2005-10-16 14:52   ` TUTORIAL.gz David Reitter
2005-10-17  8:34     ` TUTORIAL.gz Juri Linkov
2005-10-17 14:46       ` TUTORIAL.gz Stefan Monnier
2005-10-17 16:03         ` David Reitter [this message]
2005-10-17 16:20           ` TUTORIAL.gz David Kastrup
2005-10-17 17:48           ` TUTORIAL.gz Stefan Monnier
2005-10-17 18:47             ` TUTORIAL.gz Lennart Borgman
2005-10-17 19:08               ` TUTORIAL.gz Stefan Monnier
2005-10-17 19:33                 ` TUTORIAL.gz Lennart Borgman
2005-10-18  8:04                   ` TUTORIAL.gz Juri Linkov
2005-10-17 14:59     ` TUTORIAL.gz Eli Zaretskii
2005-10-17 15:22       ` TUTORIAL.gz Romain Francoise
  -- strict thread matches above, loose matches on Subject: below --
2005-10-14 11:25 TUTORIAL.gz LENNART BORGMAN
2005-10-15 12:43 ` TUTORIAL.gz Eli Zaretskii
2005-10-15 19:19   ` TUTORIAL.gz David Kastrup

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=4715FA60-84CE-4FCE-9F68-644D8C63AE73@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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.