unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: William Xu <william.xwl@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: set input/output coding system for term-mode
Date: Wed, 13 Jun 2007 17:52:19 +0800	[thread overview]
Message-ID: <87myz4ji5o.fsf@www.williamxu.com> (raw)
In-Reply-To: BF007C83-50F2-4382-B61C-2C4241BE66B6@Web.DE

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

   Am 13.06.2007 um 10:51 schrieb William Xu:

   >    each with a different encoding,
   >
   > Isn't this my original problem?

   No – as far as I understood. You wanted to change the single buffer's
   encoding "on-the-fly," having in it segments in encoding a or  encoding
   b or encoding c or ...

   Check whether there is a hook that can set the encoding for a *shell*
   or *terminal* buffer when it is created and give it a unique name, too.

It doesn't matter whether it can be set "on-the-fly" or not. i will
simply have one single *terminal* buffer. *terminal* has a
term-setup-hook, i add the following to it:

,----
| (defun xwl-term-setup-hook ()
|   (set-buffer-process-coding-system 'gb2312 'gb2312)
|   (set-buffer-file-coding-system 'gb2312 'gb2312)
|   (set-terminal-coding-system 'gb2312))
| 
| (add-hook 'term-setup-hook 'xwl-term-setup-hook)
`----

But still without luck..

-- 
William

  reply	other threads:[~2007-06-13  9:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  2:37 set input/output coding system for term-mode William Xu
2007-06-12  3:22 ` Eli Zaretskii
2007-06-12  4:37   ` William Xu
2007-06-12  9:24     ` Peter Dyballa
2007-06-13  4:29       ` William Xu
2007-06-13  8:35         ` Peter Dyballa
2007-06-13  8:51           ` William Xu
2007-06-13  9:19             ` Peter Dyballa
2007-06-13  9:52               ` William Xu [this message]
2007-06-12  4:15 ` ssSslang
2007-06-12  4:42   ` William Xu

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=87myz4ji5o.fsf@www.williamxu.com \
    --to=william.xwl@gmail.com \
    --cc=help-gnu-emacs@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.
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).