unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "B.T. Raven" <ejmn@cpinternet.com>
Subject: Re: \201 chars showing up in buffer when using emacs from mutt
Date: Thu, 24 Mar 2005 18:39:42 -0600	[thread overview]
Message-ID: <1146nfe3solhd5@corp.supernews.com> (raw)
In-Reply-To: mailman.114.1111668219.28103.help-gnu-emacs@gnu.org


<Dirk-Jan.Binnema@nokia.com> wrote in message
news:mailman.114.1111668219.28103.help-gnu-emacs@gnu.org...
Hi all,

I am using emacs as the editor for mutt; however, I have never been able
to get it working correctly, as quite often emacs will not detect that
a text file is, in fact utf8 (that's when i get the '\201' character
before
accented characters like in German). I've found similar problems on the
mailing list, but no solution that seems to work; that includes setting
utf8
as the preferred encoding.Also, it does not really seem to
matter what charset I use in mutt, or my exact setting in .emacs.

So does anyone have bullet proof settings such that I will never see
that
dreaded \201 again? I am *almost* capabable of just removing them trough
some
hook function when I start emacs, but taht seems very evil.

Thanks in advance
Dirk.

The next time you see all the characters correctly displayed in the
buffer, put

;; -*- coding: utf-8 -*-

at the top of the file. Then type C-x RET f utf-8 before saving the
buffer again. This explicit hint in the first line of the file will
prevent emacs from considering any other encoding when it reads the file
again. I don't know what mutt is but if it executes the text file, maybe
the line starting with ;; could be wrapped in another kind of multi-line
comment (like /*....*/ in C)

C-x RET I  utf-8 should also work since (I think)
default-buffer-file-coding-system's value is persistent across sessions.
Alternatively you could set currentl-language-environment with M-x
customize but then you would get the rtf1345 input method which probably
doesn't work (w32) or maybe you don't want.

Ed.

       reply	other threads:[~2005-03-25  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.114.1111668219.28103.help-gnu-emacs@gnu.org>
2005-03-25  0:39 ` B.T. Raven [this message]
2005-03-29 11:09 \201 chars showing up in buffer when using emacs from mutt Dirk-Jan.Binnema
  -- strict thread matches above, loose matches on Subject: below --
2005-03-24 12:14 Dirk-Jan.Binnema
2005-03-25  1:12 ` Peter Dyballa

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=1146nfe3solhd5@corp.supernews.com \
    --to=ejmn@cpinternet.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 read-only IMAP folder(s) and NNTP newsgroup(s).