unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marco De Vitis <starless@spin.it>
To: help-gnu-emacs@gnu.org
Subject: Re: 8-bit characters input
Date: Thu, 12 Apr 2007 15:32:08 GMT	[thread overview]
Message-ID: <YhsTh.5597$uJ5.96835@twister2.libero.it> (raw)
In-Reply-To: <jwvslb7c8d6.fsf-monnier+gnu.emacs.help@gnu.org>

Il 11/04/2007 16:14, Stefan Monnier ha scritto:

>> C-v C-h l
> 
> Hmm... that's odd.. And that's with OSX's Terminal.app?
> I get full utf-8 coding there, without having changed any part of the config.

Yes, OSX's Terminal.app.
I actually have customized the Terminal config somehow a long time ago, 
to be able to correctly input and read utf-8 in Terminal itself...

> I'm not sure what you mean by "configured as xterm-color".

I mean that OSX's Terminal is set, through its preferences, to declare 
the terminal type as xterm-color. Or, in other words, that the env var 
$TERM is set to "xterm-color".

>> I now tried also from PuTTy (configured as xterm) on a Windows machine, and
>> hitting à appears to send different stuff:
> 
>> M-C M-SPC C-h l
> 
> That looks much better.  Actually it looks almost like utf-8.  Have you
> tried C-x RET k utf-8 RET when logged in this way?

I did now, and indeed it works!
And then... it also works in Terminal.app, as long as I open 
Terminal.app's window preferences and deactivate the "Escape non-ASCII 
chars" option in the Emulation section; indeed, when this option is not 
active, pressing "à" in emacs sends the same codes which were sent using 
PuTTy.

So, I can now use 8-bit chars in emacs by putting 
(set-keyboard-coding-system 'utf-8)
in my ~/.emacs file, and deactivating that Terminal option when I'm on 
OSX; the only problem is that I need that option to correctly input 
8-bit chars in Terminal's "normal" usage, i.e. when using it locally, 
without connecting to a remote machine... I'll try to live with it.

Thanks a lot.

-- 
Ciao,
   Marco.

  reply	other threads:[~2007-04-12 15:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 16:10 8-bit characters input Marco De Vitis
2007-04-06 17:38 ` Eli Zaretskii
     [not found] ` <mailman.1815.1175881310.7795.help-gnu-emacs@gnu.org>
2007-04-06 21:30   ` Marco De Vitis
2007-04-06 21:36 ` Peter Dyballa
     [not found] ` <mailman.1819.1175895648.7795.help-gnu-emacs@gnu.org>
2007-04-07  0:03   ` Marco De Vitis
2007-04-09 20:03 ` Stefan Monnier
2007-04-09 23:18   ` Marco De Vitis
2007-04-11  3:44     ` Stefan Monnier
2007-04-11  8:59       ` Marco De Vitis
2007-04-11 11:46         ` Peter Dyballa
2007-04-11 14:14         ` Stefan Monnier
2007-04-12 15:32           ` Marco De Vitis [this message]
2007-04-12 22:41             ` Stefan Monnier
2007-04-13  6:38               ` Marco De Vitis
     [not found]         ` <mailman.1946.1176292242.7795.help-gnu-emacs@gnu.org>
2007-04-12 14:58           ` Marco De Vitis

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='YhsTh.5597$uJ5.96835@twister2.libero.it' \
    --to=starless@spin.it \
    --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).