[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What does `undecided' do for encoding text?

From: Kenichi Handa
Subject: Re: What does `undecided' do for encoding text?
Date: Mon, 16 Feb 2009 20:44:44 +0900

In article <address@hidden>, Stefan Monnier <address@hidden> writes:

>>> It looks like `undecided' works the same as `raw-text' for encoding
>>> text.  Is that true in general?
> > Yes.  More exactly, it is the same as `raw-text-unix'.

> Which I prefer calling `binary'.

What do you mean by "calling"?

raw-text-unix and binary are different when
coding-system-change-text-conversion and
coding-system-change-eol-conversion are called.

>>> I think this should be reflected in the ELisp manual.
> > I don't think so because it is just a fallback behavior, and
> > Elisp programmer should avoid specifying `undecided' on
> > encoding.

> Then why do we even allow it?  We should signal an error.

It seems difficult to find a good point of signaling an
error.  At least, visiting an ascii only file, inputting
ascii only, and saving it should be a valid operation.  At
that time, buffer-file-coding-system is undecided-unix.

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]