Re: v24.3.1: set-terminal-coding-system is not working when connecting to the server through a new frame

[varun <varun.net@gmail.com>]

Thanks Stefan for the responding.

I looked at the init.el file and have the following entry that sets the
locale:
(setq locale-coding-system 'utf-8)

Is this not enough or am I not using it correctly?


Got these from:
https://stackoverflow.com/questions/2901541/which-coding-system-should-i-use-in-emacs
(setq utf-translate-cjk-mode nil) ; disable CJK coding/encoding
(Chinese/Japanese/Korean characters)
  (set-language-environment 'utf-8)
  (set-keyboard-coding-system 'utf-8-mac) ; For old Carbon emacs on OS X
only
  (setq locale-coding-system 'utf-8)
  (set-default-coding-systems 'utf-8)
  (set-terminal-coding-system 'utf-8)
  (unless (eq system-type 'windows-nt)
   (set-selection-coding-system 'utf-8))
  (prefer-coding-system 'utf-8)

Thanks



On Fri, Jan 31, 2014 at 8:23 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:

> > I have been having this problem in v24.3 (worked fine in v23.1.1). When I
> > try to connect to the server from a new frame created by running the
> > command emacsclient -nw -c filename, it does not set the terminal coding
> > system (init.el: (set-terminal-coding-system 'utf-8)).
>
> set-terminal-coding-system changes the coding system of the *current*
> terminal, so it does not affect terminals you might create later
> (e.g. with emacsclient).
>
> You might like to use tty-setup-hook to run set-terminal-coding-system
> after every emacsclient connection.  But a simpler solution might be to
> make sure your locale is using utf-8, so that Emacs's terminals will all
> default to using utf-8 as well.
>
>
>         Stefan
>
>
>