From: Steve Youngs <youngs@xemacs.org>
Cc: Carsten Dominik <dominik@astro.uva.nl>
Subject: Re: [Carsten Dominik <dominik@astro.uva.nl>] Re: lisp/ChangeLog corruption
Date: Thu, 25 Jul 2002 03:01:14 +1000 [thread overview]
Message-ID: <microsoft-free.x44repawmd.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <200207241554.g6OFsBT05724@aztec.santafe.edu> (Richard Stallman's message of "Wed, 24 Jul 2002 09:54:11 -0600")
|--==> "RS" == Richard Stallman <rms@gnu.org> writes:
Carsten Dominik <dominik@astro.uva.nl> wrote:
> I have been using XEmacs 21.1 patch 14 (Mule) to check edit and check
> in the file. I don't know why it would change the coding system, but
> maybe it does. I don't know much about coding systems...
Carsten, this might help (untested):
(if (featurep 'mule)
(progn
(define-coding-system-alias 'iso-2022-7bit-unix 'iso-2022-7bit)
(add-to-list 'file-coding-system-alist '("ChangeLog" . iso-2022-7bit-unix))))
RS> Please don't do this with XEmacs any more. Please use Emacs.
Why? Providing that the above prevents any future file corruption in
the ChangeLogs, it shouldn't matter should it?
RS> (Besides, the only way you can test your changes in Emacs is to use
RS> Emacs.)
True, but it's not often that you need to test changes to a ChangeLog
file. :-)
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs@xemacs.org>---|
next prev parent reply other threads:[~2002-07-24 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86znwijf6u.fsf@gerd.free-bsd.org>
2002-07-24 15:54 ` [Carsten Dominik <dominik@astro.uva.nl>] Re: lisp/ChangeLog corruption Richard Stallman
2002-07-24 17:01 ` Steve Youngs [this message]
2002-07-25 4:53 ` Eli Zaretskii
2002-07-28 22:14 ` Steve Youngs
2002-07-25 18:07 ` Richard Stallman
2002-07-28 22:25 ` Steve Youngs
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=microsoft-free.x44repawmd.fsf@eicq.dnsalias.org \
--to=youngs@xemacs.org \
--cc=dominik@astro.uva.nl \
/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).