all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: No coding system in the modeline for unibyte buffers.
Date: Fri, 16 Jan 2009 15:45:35 -0500	[thread overview]
Message-ID: <jwviqofrneo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f7ccd24b0901160846p74ec2098s83ed701a41566c0b@mail.gmail.com> (Juanma Barranquero's message of "Fri, 16 Jan 2009 17:46:23 +0100")

>> So as to indicate if the buffer is unibyte or multibyte?

> Hmm. I suppose that is useful (though, if the coding system is on the
> modeline, its toltip will tell you that). Knowing the encoding is
> useful, too, if you deal with unibyte data from various encodings.
> Perhaps both things could be shown.

Maybe the problem is that you don't realize that a unibyte buffer is
different from a multibyte buffer using raw-text (or binary) encoding?


        Stefan




  reply	other threads:[~2009-01-16 20:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 15:59 No coding system in the modeline for unibyte buffers Juanma Barranquero
2009-01-16 16:36 ` 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 [this message]
2009-01-16 23:47       ` Juanma Barranquero
2009-01-17  2:11         ` Stefan Monnier
2009-01-17  2:24           ` Juanma Barranquero
2009-01-20  6:15             ` bug#1935: marked as done (describe-char does not show raw bytes as such) Emacs bug Tracking System
2009-01-17  2:24           ` bug#1935: No coding system in the modeline for unibyte buffers 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwviqofrneo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.