unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <Dirk-Jan.Binnema@nokia.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: \201 chars showing up in buffer when using emacs from mutt
Date: Tue, 29 Mar 2005 14:09:28 +0300	[thread overview]
Message-ID: <D8ECD0B6B0695144A6C2C000997D6BF445202F@esebe105.NOE.Nokia.com> (raw)

Thank you for your reply.

> From: Peter_Dyballa@Web.DE [mailto:Peter_Dyballa@Web.DE]
> 
> Am 24.03.2005 um 13:14 schrieb <Dirk-Jan.Binnema@nokia.com>:
> 
> > 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.
> >
> 
> You have a few choices:
> 
> a) set in the file's header something like
> 	<comment> -*- coding: utf-8 -*-
>     where <comment> is the comment character for this type of file

Ah... but that would require a bit of a hack though in my use case 
(running emacs as the editor for mutt).

> b) set file-coding-system-alist, auto-coding-alist -- You can 
> customize 
> this variable:
> 	 ("\\.tex\\'" iso-latin-9-unix . iso-latin-9-unix)
> 
> c) some of these:
 
  [...]

> d) combinations of above

Ok, I am testing these. I did however also discover the 'send_charset'
setting for Mutt; together with your hints that may do the trick -- thanks.

--Dirk.

             reply	other threads:[~2005-03-29 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 11:09 Dirk-Jan.Binnema [this message]
     [not found] <mailman.114.1111668219.28103.help-gnu-emacs@gnu.org>
2005-03-25  0:39 ` \201 chars showing up in buffer when using emacs from mutt B.T. Raven
  -- 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=D8ECD0B6B0695144A6C2C000997D6BF445202F@esebe105.NOE.Nokia.com \
    --to=dirk-jan.binnema@nokia.com \
    --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).