[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: diacritics in emacs but not in emacsclient

From: Bob Proulx
Subject: Re: diacritics in emacs but not in emacsclient
Date: Wed, 2 Jul 2014 17:51:55 -0600
User-agent: Mutt/1.5.23 (2014-03-12)

Tom Koornwinder wrote:
> From my mac, working in a console window provided by Terminal, I am used to
> login by ssh on a server which is running on bash.
> It has GNU Emacs 23.1.1.

Sounds like many Debian Wheezy Stable boxes.  :-)  Of course it could
be any of many other distributions too.

> In emacs windows I can produce diacritics like e accent grave or o umlaut
> in the usual Mac way by the option (= alt) key:
> option-` e  and option-u o.

If that is produced in the terminal then it should be sent down the
ssh wire too and appear in the remote shell.  And if that works then
it should also appear in emacs.

> However, when I prepare an email message in mutt in an emacs window
> provided by emacsclient then I cannot produce these diacritics.
> The mentioned symbols now give C( and C6 .

Stefan Monnier suggested that perhaps you have not set LANG
appropriately and will need to set it to a UTF charset.  I agree.

It appears that you are using a Compose key for composing those
characters.  I wanted to suggest that you could use emacs own compose
key "C-x 8".  It provides compose key capability in emacs and dates
from before systems generally had their own Compose key defined and
therefore could work anywhere.  Please try this:

  C-x 8 ' e  produces é
  C-x 8 " o  produces ö

That is mostly for debug data collection as it provides a data point
on whether emacs can handle the characters or not.

> The same happens when I copy these (correctly displayed) symbols from
> a text window and paste them in my mail window: C( and  C6 .

Does that work locally when working on a local terminal not logged in
anywhere remotely?  Does that work when logged in remotely to the
command line shell?  Then try it into an remote shell running emacs.

If it does not work locally then it is a local localization problem.
If it works locally but not remotely then the remote terminal has a
localization problem.  If it works remotely in a terminal but not
emacs then it is an emacs problem.

Be sure to test emacs with "emacs -q" and "emacs -Q" to avoid any
possibility of local customization causing problems.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]