unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Kevin Rodgers" <kevin.d.rodgers@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: coding systems and input methods are non-intuitive stuff
Date: Tue, 30 Jan 2007 09:38:07 +0100	[thread overview]
Message-ID: <f7ccd24b0701300038p28e73d5ds86bf2cc65ede02a9@mail.gmail.com> (raw)
In-Reply-To: <epmuv3$56p$1@sea.gmane.org>

On 1/30/07, Kevin Rodgers <kevin.d.rodgers@gmail.com> wrote:

> So how does U+015F get inserted into a latin-1 buffer?

C-x RET f is `set-buffer-file-coding-system'. In other words, it will
apply when I try to save the buffer; and then possibly I'll get a
message saying that the buffer's contents cannot be saved with that
coding system. But that is irrelevant. There's nothing wrong with

 ;; insert whatever stuff
 ;; set buffer coding system 1
 ;; insert stuff not representable in coding system 1
 ;; set buffer coding system 2
 ;; save the file

There's no requirement that the contents of a buffer *must* be
writable with the current buffer coding system, unless and until I try
to save it...

But that's a digression. What I'm interested in knowing is whether
being able to do

  ;; insert a char with the current input method
  ;; M-x quail-show-key => "X can't be input with the current input method"

(as in my previous example) is a bug or a "feature" of the
buffer-coding-system / input method interaction.

                    /L/e/k/t/u

  parent reply	other threads:[~2007-01-30  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 17:11 coding systems and input methods are non-intuitive stuff Juanma Barranquero
2007-01-30  8:17 ` Kevin Rodgers
2007-01-30  8:35   ` David Kastrup
2007-01-30  8:38   ` Juanma Barranquero [this message]
2007-01-30 12:46 ` Kenichi Handa
2007-01-30 12:58   ` Juanma Barranquero
2007-01-31  0:46     ` Kenichi Handa
2007-01-31  2:12       ` Juanma Barranquero
2007-02-01  1:48         ` Kenichi Handa
2007-02-01  1:54           ` Juanma Barranquero

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=f7ccd24b0701300038p28e73d5ds86bf2cc65ede02a9@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kevin.d.rodgers@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 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).