From: Cyprian Laskowski <swagbelly@yahoo.com>
Subject: coding-system difficulties
Date: Wed, 13 Nov 2002 15:21:53 GMT [thread overview]
Message-ID: <m33cq5h4g4.fsf@swagbelly.net> (raw)
Hi,
I've never really totally understood coding-system issues. Here's a
recurring problem:
Sometimes I get email in non-English characters: sometimes Gnus shows
a readable version, sometimes not (even though both cases sometimes
arise with the same people). But the following little sequence lets
me read:
C-x h
M-w
C-x C-f ~/tmp/weird_mail.txt RET
C-y
C-x C-s
C-x C-v RET
I'm not sure why this behaves differently, or how to proceed properly:
but I'm sure that it's not by binding this keyboard macro to `C-f'. :)
cyp
next reply other threads:[~2002-11-13 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 15:21 Cyprian Laskowski [this message]
[not found] ` <84y97x5utn.fsf@lucy.cs.uni-dortmund.de>
2002-11-14 5:33 ` Cyprian Laskowski
2002-11-14 14:18 ` Kai Großjohann
[not found] ` <m31y5oc8yo.fsf@swagbelly.net>
[not found] ` <843cq3hn3g.fsf@lucy.cs.uni-dortmund.de>
2002-11-15 5:49 ` Fredrik Staxeng
[not found] ` <1mr8dps4ix.fsf@Tempo.Update.UU.SE>
[not found] ` <v9wunhckt2.fsf@marauder.physik.uni-ulm.de>
[not found] ` <m3bs4sg069.fsf@swagbelly.net>
2002-11-14 12:23 ` Fredrik Staxeng
2002-11-14 13:01 ` Hugh Baker
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=m33cq5h4g4.fsf@swagbelly.net \
--to=swagbelly@yahoo.com \
/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 NNTP newsgroup(s).