From: "Richard M. Stallman" <rms@gnu.org>
Cc: david.reitter@gmail.com, emacs-devel@gnu.org
Subject: Re: TUTORIAL.gz
Date: Sat, 15 Oct 2005 12:13:23 -0400 [thread overview]
Message-ID: <E1EQoex-0004gw-JW@fencepost.gnu.org> (raw)
In-Reply-To: <20051014.125112.08653741.wl@gnu.org> (message from Werner LEMBERG on Fri, 14 Oct 2005 12:51:12 +0200 (CEST))
> I don't see the point in doing that when the info manuals remain
> uncompressed at the same time.
Well, then let's compress the info files too.
It is not crucial whether we do this. (That is not just an Emacs
question.) The point is, accessing compressed info files works; if
the sysadmin compresses them, it works.
The proposal here is that accessing compresses tutorial files should
work too. But since that is just an Emacs question, we might then
want to distribute them compressed.
next prev parent reply other threads:[~2005-10-15 16:13 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 ` Richard M. Stallman [this message]
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 ` TUTORIAL.gz David Reitter
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=E1EQoex-0004gw-JW@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@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.