From: Richard Stallman <rms@gnu.org>
Cc: eliz@is.elta.co.il, keichwa@gmx.net, emacs-devel@gnu.org
Subject: Re: lisp/ChangeLog coding system
Date: Mon, 29 Apr 2002 12:39:30 -0600 (MDT) [thread overview]
Message-ID: <200204291839.g3TIdU206284@aztec.santafe.edu> (raw)
In-Reply-To: <200204282319.g3SNJBM13441@rum.cs.yale.edu> (monnier+gnu/emacs@RUM.cs.yale.edu)
He might be referring to the fact that saving a file with encoding
foo when the first line says "-*- coding: bar -*-" will lead to
corruption.
Could you describe the complete scenario in which this might happen?
If the user explicitly asks for it, it might be a mistake but it isn't
Emacs's fault. If it happens in some other scenario, perhaps Emacs
needs to be changed.
But of the course the first question (the one RMS asked IIUC) is why
did Emacs not use iso-2202 despite the -*- coding: -*- tag.
I did not have anything that specific in mind.
I'm just trying to get to the bottom of the situation.
next prev parent reply other threads:[~2002-04-29 18:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 14:45 lisp/ChangeLog coding system Gerd Moellmann
2002-04-27 22:41 ` Richard Stallman
2002-04-27 23:05 ` Michael Kifer
2002-04-29 5:01 ` Eli Zaretskii
2002-04-29 11:22 ` Gerd Moellmann
2002-04-29 13:33 ` Eli Zaretskii
2002-04-30 5:18 ` Richard Stallman
2002-04-30 5:31 ` Eli Zaretskii
2002-05-01 7:13 ` Richard Stallman
2002-05-01 11:56 ` Eli Zaretskii
2002-04-29 5:06 ` Richard Stallman
2002-04-29 6:10 ` Michael Kifer
2002-04-29 10:00 ` Eli Zaretskii
2002-04-30 5:18 ` Richard Stallman
2002-04-30 5:19 ` Richard Stallman
2002-04-30 5:22 ` Michael Kifer
2002-04-30 5:32 ` Eli Zaretskii
2002-04-30 5:53 ` Michael Kifer
2002-04-30 9:19 ` Eli Zaretskii
2002-04-30 15:35 ` Michael Kifer
2002-04-28 3:06 ` Karl Eichwalder
2002-04-28 18:22 ` Eli Zaretskii
2002-04-28 23:19 ` Stefan Monnier
2002-04-29 5:03 ` Eli Zaretskii
2002-04-29 18:39 ` Richard Stallman [this message]
2002-04-29 1:10 ` Stephen J. Turnbull
2002-04-29 1:55 ` Stefan Monnier
2002-04-29 5:07 ` Eli Zaretskii
2002-04-29 11:28 ` Stephen J. Turnbull
2002-04-29 11:49 ` Miles Bader
2002-04-29 13:31 ` Stefan Monnier
2002-04-29 15:54 ` Stephen J. Turnbull
2002-04-29 15:56 ` Karl Eichwalder
2002-04-29 16:38 ` Miles Bader
2002-04-29 13:43 ` Eli Zaretskii
2002-04-29 5:05 ` Richard Stallman
2002-04-29 15:52 ` Karl Eichwalder
2002-04-29 16:37 ` Stefan Monnier
2002-04-29 18:43 ` Eli Zaretskii
2002-04-29 18:41 ` Eli Zaretskii
2002-04-29 19:12 ` Simon Josefsson
2002-04-30 4:35 ` Eli Zaretskii
2002-04-30 8:50 ` Simon Josefsson
2002-04-30 5:19 ` Richard Stallman
2002-04-30 18:09 ` Karl Eichwalder
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=200204291839.g3TIdU206284@aztec.santafe.edu \
--to=rms@gnu.org \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=keichwa@gmx.net \
/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).