[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
No coding system in the modeline for unibyte buffers.
From: |
Juanma Barranquero |
Subject: |
No coding system in the modeline for unibyte buffers. |
Date: |
Fri, 16 Jan 2009 16:59:48 +0100 |
Obviously, not a bug:
1997-07-29 Richard Stallman <address@hidden>
* xdisp.c (decode_mode_spec_coding): If multibyte chars disabled.
display only the eol flag.
But, why?
Currently,
C-x C-b new <RET>
-*- coding: raw-text-unix -*- <RET>
C-x C-s new.txt <RET> ;; -t(Unix)--- new.txt [etc]
C-x C-k
C-x C-f new.txt <RET> ;; -(Unix)--- new.txt [etc]
which works as expected but it's weird.
Is there any downside to just removing the code that forces that behavior?
Juanma
Index: src/xdisp.c
===================================================================
RCS file: /sources/emacs/emacs/src/xdisp.c,v
retrieving revision 1.1275
diff -u -2 -r1.1275 xdisp.c
--- src/xdisp.c 10 Jan 2009 18:41:07 -0000 1.1275
+++ src/xdisp.c 16 Jan 2009 12:24:56 -0000
@@ -18238,5 +18238,4 @@
{
Lisp_Object val;
- int multibyte = !NILP (current_buffer->enable_multibyte_characters);
const unsigned char *eol_str;
int eol_str_len;
@@ -18249,6 +18248,5 @@
if (!VECTORP (val)) /* Not yet decided. */
{
- if (multibyte)
- *buf++ = '-';
+ *buf++ = '-';
if (eol_flag)
eoltype = eol_mnemonic_undecided;
@@ -18263,6 +18261,5 @@
eolvalue = AREF (val, 2);
- if (multibyte)
- *buf++ = XFASTINT (CODING_ATTR_MNEMONIC (attrs));
+ *buf++ = XFASTINT (CODING_ATTR_MNEMONIC (attrs));
if (eol_flag)
- No coding system in the modeline for unibyte buffers.,
Juanma Barranquero <=
Re: No coding system in the modeline for unibyte buffers., Richard M Stallman, 2009/01/17