From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
"Kai Großjohann" <Kai.Grossjohann@CS.Uni-Dortmund.DE>,
"Andreas Schwab" <schwab@suse.de>,
emacs-devel@gnu.org
Subject: Re: ChangeLog and unification
Date: Wed, 20 Feb 2002 10:04:54 -0500 [thread overview]
Message-ID: <200202201504.g1KF4sJ20610@rum.cs.yale.edu> (raw)
In-Reply-To: Pine.SUN.3.91.1020220081524.21448C@is
> > The unify-on-encode is safe and does not do unification.
> What will it do if you yank a string with Latin-2 characters and then
> save the buffer? Assuming that buffer-file-coding-system is
> iso-2022-7bit, will it save those Latin-2 characters as Latin-2 or as
> Latin-1?
Latin-2 AFAIK, but I'll let you double check.
> > Actually, I can't even think of any reason
> > why we should try to make it possible to turn it off.
> That is almost certainly a bad idea: it should be possible to turn off
> _any_ feature, certainly a Mule-related one. Someone, some day, will
> want that.
Based on my understanding of the code, the only effect of unify-on-encode
is to increase the number of coding-systems that can be used for a given
buffer. If you don't use one of the added coding-systems, the output
should be exactly the same as before.
Thus if you don't want the feature, you can use C-x RET f to specify
another coding-system.
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
prev parent reply other threads:[~2002-02-20 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 8:02 ChangeLog and unification Eli Zaretskii
2002-02-16 16:14 ` Kai Großjohann
2002-02-17 16:49 ` Richard Stallman
2002-02-16 16:53 ` Andreas Schwab
2002-02-16 18:05 ` Eli Zaretskii
2002-02-17 9:43 ` Kai Großjohann
2002-02-18 17:06 ` Stefan Monnier
2002-02-19 21:31 ` Richard Stallman
2002-02-20 6:27 ` Eli Zaretskii
2002-02-20 6:25 ` Eli Zaretskii
2002-02-20 15:04 ` Stefan Monnier [this message]
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=200202201504.g1KF4sJ20610@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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).