From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, user42@zip.com.au, emacs-devel@gnu.org
Subject: Re: arc-lzh-exe.el -- archive-mode on lzh self-extracting exes
Date: Sat, 21 Apr 2007 14:25:10 -0400 [thread overview]
Message-ID: <E1HfKGk-0001rW-NN@fencepost.gnu.org> (raw)
In-Reply-To: <uirbqgj9e.fsf@gnu.org> (message from Eli Zaretskii on Sat, 21 Apr 2007 12:38:05 +0300)
> If that change is to simply recognize a new kind of archive, why delay
> it?
Because .exe files are much more widespread than LZH archive in .exe
disguise. So the change in point might adversely affect many files.
Indeed, nost files named .exe are not LZH archives.
It would not be right at all to treat them as LZH archives.
I see only two ways to handle the .exe LZH archives:
1. Detect them automatically (probably complex).
2. Have users say explicitly when they want to treat a .exe file
that way.
#2 is probably best. Does that currently work?
Does it work to visit the .exe file normally and then
do M-x archive-mode?
If so, this isalready exactly as it should be.
next prev parent reply other threads:[~2007-04-21 18:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zm5etm0r.fsf@zip.com.au>
[not found] ` <E1HcAoA-0001sC-G4@fencepost.gnu.org>
[not found] ` <87tzvitz4z.fsf@zip.com.au>
2007-04-19 1:41 ` arc-lzh-exe.el -- archive-mode on lzh self-extracting exes Kevin Ryde
2007-04-19 2:01 ` Kevin Ryde
2007-04-19 23:17 ` Richard Stallman
2007-04-19 23:58 ` Chong Yidong
2007-04-20 1:05 ` Stefan Monnier
2007-04-20 1:42 ` Kevin Ryde
2007-04-20 10:40 ` Eli Zaretskii
2007-04-20 21:53 ` Richard Stallman
2007-04-20 22:44 ` Chong Yidong
2007-04-21 9:38 ` Eli Zaretskii
2007-04-21 18:25 ` Richard Stallman [this message]
2007-04-21 19:22 ` Chong Yidong
2007-04-22 23:46 ` Kevin Ryde
2007-04-23 14:25 ` Chong Yidong
2007-04-20 10:37 ` Eli Zaretskii
2007-04-20 10:44 ` 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
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=E1HfKGk-0001rW-NN@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=user42@zip.com.au \
/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).