From: Juanma Barranquero <lekktu@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: No coding system in the modeline for unibyte buffers.
Date: Fri, 16 Jan 2009 16:59:48 +0100 [thread overview]
Message-ID: <f7ccd24b0901160759g22c47a2dl59a47fa554923122@mail.gmail.com> (raw)
Obviously, not a bug:
1997-07-29 Richard Stallman <rms@psilocin.gnu.ai.mit.edu>
* 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)
next reply other threads:[~2009-01-16 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 15:59 Juanma Barranquero [this message]
2009-01-16 16:36 ` No coding system in the modeline for unibyte buffers Eli Zaretskii
2009-01-16 16:42 ` Juanma Barranquero
2009-01-16 16:42 ` Stefan Monnier
2009-01-16 16:46 ` Juanma Barranquero
2009-01-16 20:45 ` Stefan Monnier
2009-01-16 23:47 ` Juanma Barranquero
2009-01-17 2:11 ` Stefan Monnier
2009-01-17 2:24 ` Juanma Barranquero
2009-01-17 17:03 ` Richard M Stallman
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=f7ccd24b0901160759g22c47a2dl59a47fa554923122@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
/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).