From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: Unify on encoding
Date: Tue, 19 Mar 2002 13:17:55 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1020319130726.17982B-100000@is> (raw)
In-Reply-To: <200203190844.g2J8iGC09206@wijiji.santafe.edu>
On Tue, 19 Mar 2002, Richard Stallman wrote:
> I'm guessing that quite a few people are using the CVS version nowadays,
> so the option was, in a certain sense, ``released''.
>
> As a matter of principle, this is NOT a reason to keep a feature which
> we decide is unnecessary. People who use the CVS version do so at
> their own risk.
This is a misunderstanding. The current mode of operation of released
Emacs versions is that there's no unification on encoding. The CVS code
added an option to turn on that unification. Stefan's question was about
whether turning it on by default (to which I didn't object) should be
accompanied by removing the possibility to turn it off.
I only objected to the latter part, because doing so would change an
important characteristic of the default operation without leaving an
escape route for users who don't want the new default. I don't think
I've ever seen defaults changed in Emacs without some option to go back.
In other words, the option that was recommended to be removed ``exists''
in the released version--in the current default operation mode.
> Let's take it out and see if anyone complains.
What's the rush? An option that is turned off cannot possibly do any
harm. Bitter experience with Mule should have taught us that we
shouldn't make changes without a good reason. Isn't it better to get
some experience from having unification turned on by default?
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-19 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 22:28 Unify on encoding Stefan Monnier
2002-03-18 6:29 ` Eli Zaretskii
2002-03-18 14:33 ` Stefan Monnier
2002-03-18 16:10 ` Eli Zaretskii
2002-03-19 8:44 ` Richard Stallman
2002-03-19 11:17 ` Eli Zaretskii [this message]
2002-03-19 19:19 ` Jason Rumney
2002-03-19 21:12 ` Stefan Monnier
2002-03-20 5:56 ` Eli Zaretskii
2002-03-20 12:23 ` Stefan Monnier
2002-03-18 20:06 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 2:49 Kenichi Handa
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=Pine.SUN.3.91.1020319130726.17982B-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).