[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs Lisp's future
From: |
Eli Zaretskii |
Subject: |
Re: Emacs Lisp's future |
Date: |
Tue, 07 Oct 2014 19:59:43 +0300 |
> From: Mark H Weaver <address@hidden>
> Cc: Richard Stallman <address@hidden>, Eli Zaretskii <address@hidden>,
> address@hidden, address@hidden, address@hidden, address@hidden,
> address@hidden
> Date: Tue, 07 Oct 2014 11:15:05 -0400
>
> > UTF-8 is defined as not containing "overlong" sequences, so Emacs
> > decodes them into two raw-byte indicating characters, one indicating
> > 0xC0, one indicating 0xA2. When encoding, it reassembles them into
> > 0xC0 0xA2.
>
> When editing a file, this is probably the right default behavior,
> although ideally it should warn the user.
It does, when the user modifies the file and then saves it.
- Re: Emacs Lisp's future, (continued)
- Re: Emacs Lisp's future, Mark H Weaver, 2014/10/07
- Re: Emacs Lisp's future, David Kastrup, 2014/10/08
- Re: Emacs Lisp's future, Mark H Weaver, 2014/10/08
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/08
- Re: Emacs Lisp's future, David Kastrup, 2014/10/08
- Re: Emacs Lisp's future, Stephen J. Turnbull, 2014/10/08
- Re: Emacs Lisp's future, David Kastrup, 2014/10/09
- Re: Emacs Lisp's future, Stephen J. Turnbull, 2014/10/09
- Re: Emacs Lisp's future, David Kastrup, 2014/10/09
- Re: Emacs Lisp's future, Florian Weimer, 2014/10/11
- Re: Emacs Lisp's future,
Eli Zaretskii <=
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/07
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/08
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/08
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/09
- Re: Emacs Lisp's future, David Kastrup, 2014/10/09
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/10/09
- Re: Emacs Lisp's future, David Kastrup, 2014/10/09
- Re: Emacs Lisp's future, Mark H Weaver, 2014/10/12
- Re: Emacs Lisp's future, David Kastrup, 2014/10/13
- Re: Emacs Lisp's future, Richard Stallman, 2014/10/10