From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] strange chars in email body
Date: Wed, 10 Nov 2010 10:54:08 +0100 [thread overview]
Message-ID: <1289382791-sup-6828@ittemni> (raw)
In-Reply-To: <AANLkTik-iKeM5yiHEKdujUesQ0Frpuq7ycFQBB+CZ0ov@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 448 bytes --]
Hi,
Excerpts from Jagadeesh N. Malakannavar's message of Wed Nov 10 07:48:39 +0100 2010:
> I am seeing strange characters like
>
>
> M-b~@~S
> M-b~@~Y [for donM-b~@~Yt]
>
> In the email body. I am using
>
> $ sup -v
> sup vgit
>
> $ echo $LANG
> en_US.utf8
>
> Am I setting anything wrong?
Have you installed ncursesw gem?
--
Amadeusz Żołnowski
PGP key fpr: C700 CEDE 0C18 212E 49DA 4653 F013 4531 E1DB FAB5
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-11-10 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 6:48 Jagadeesh N. Malakannavar
2010-11-10 9:54 ` Amadeusz Żołnowski [this message]
2010-11-10 20:43 ` Philipp Überbacher
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289382791-sup-6828@ittemni \
--to=aidecoe@aidecoe.name \
--cc=sup-talk@rubyforge.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